AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
The Importance of Documentation Driven Development
Pester uses a simple testing framework called P, just letter B because it's very small. It has like 100 lines of code and we use that to automate 90% of what we're testing on Pester. Every time we have an issue, we try to create at least one new test for this that links to the issue on GitHub. But I don't really have a strong recommendation or answer as long as if you introduce a bug that you saw before, hopefully there is a best that's failing.