Test-Driven Development
In a test-driven development cycle, the process of adding a new feature or improving an existing feature works as follows:
1. Writing a test based on the feature requirements.
2. Running the test for the first time and verifying that it fails.
3. Writing the code for the new feature.
4. Running the test.
5. Refactoring the code.
6. Rerunning the test.
Typemock Isolator assists you in a test-driven development by providing powerful mocking capabilities and automating important tasks. For example, Typemock Isolator automatically runs the test for the first time (before the code is written), verifies that the test fails, and runs the required tests after the code is written.
In addition, Typemock Isolator provides the incremental code coverage feature. If you are following the test-driven development practices, your incremental coverage will always be 100%.