As we can see here:
https://github.com/PowerShell/PowerShell/tree/master/test
M$ is using Pester.
Without PowerShell, many Microsoft products would be much less useful.
If PowerShell would have even more bugs, the many Microsoft products would definitely become a nightmare.
Therefore, Microsoft is considered heavily dependent on Pester.
Why can't we find Microsoft in the support list of maintainers who spend their spare time to add the component that is so elementarily important to Microsofts product PowerShell?
I'm not a maintainer, but I am very disappointed about Microsoft's greed and the lack of appreciation.
Not a bad point.
I can't speak to how these things work, but IMO it's worth pursuing an avenue of a set amount of contribution monthly or yearly to Pester (and/or other open source tools that are heavily utilised) per team in Microsoft that uses them.
I can't speak to how these things work, but IMO it's worth pursuing an avenue of a set amount of contribution monthly or yearly to Pester (and/or other open source tools that are heavily utilised) per team that uses them.
Yeah, while the tone of the OP is not super helpful, they're not wrong.
@SteveL-MSFT it would be worth discussing a financial contribution for Pester on OpenCollective from MS. It's by far the single most important and impactful PowerShell community project.
There are many ways that companies contribute to open-source, and this is outside the scope of this repository.
Please make sure to adhere to our Code of Conduct as well
Most helpful comment
Yeah, while the tone of the OP is not super helpful, they're not wrong.
@SteveL-MSFT it would be worth discussing a financial contribution for Pester on OpenCollective from MS. It's by far the single most important and impactful PowerShell community project.