This shows that there is a feature missing. You run your test suite and make sure all the new tests fail. Before you add any new feature you write a set of tests for it. In TDD you write the specification in the form of tests.
PESTER TESTING CODE
First you define how the code should work and then you write the code. TDD is turning this around, so you progress from specification to implementation. You are progressing from implementation (how the code is written) to specification (how it should work).
Traditionally you write your functional code first and then you write tests for it. Pester is best used with TDD approach to development.įor those of you who are not familiar with TDD, let me sum it up briefly: TDD is the opposite of the traditional approach to development.
This makes it great for both black-box and white-box testing. Pester implements a test drive to isolate your test files, and it can replace almost any command in PowerShell with your own implementation. It provides a few simple-to-use keywords that let you create tests for your scripts. Pester is a unit testing framework for PowerShell. To help you with the first steps, I wrote a short series of articles that describe the basics of Pester. Armed with this knowledge I was finally able to put Pester in use, and found it useful through the whole life cycle of my scripts. It took me reading a book on Test-Driven-Development (TDD) to understand what the ideas behind Pester are, and that they are actually pretty simple. This seemed to be super-useful for my day-to-day scripting, but unfortunately the learning curve was a bit steeper than I thought it would be. Some time ago I stumbled upon the Pester framework that promised I would be able to test my scripts.
0 kommentar(er)
