Quoting:
"The idea of continuous testing is to make this feedback loop even more tight. The tests should be run automatically whenever the code changes and the developer should not need to run them manually.
"The idea of continuous testing is to make this feedback loop even more tight. The tests should be run automatically whenever the code changes and the developer should not need to run them manually.
This can prove useful even if the developer only writes tests, after he has written the code under test. When he needs to refactor or enhance existing code, these tests will take on the role of regression tests, i.e. they will serve as a safety net from breaking original functionality.
However, continuous testing shows its real worth when the tests are written in advance or in parallel with the code under test, as required by Test Driven Development (TDD)."
Tools include:
"(...) three competing solutions available:
"(...) three competing solutions available:
- NCrunch from Remco Software,
- DotCover by JetBrains, sold as a part of ReSharper Ultimate bundle, and...
- Smart Runner by Typemock, sold together with Typemock Isolator for .NET.
Microsoft’s first shy attempt in this field was a feature that was added to Test Explorer: Run Tests After Build switch made it possible to automatically run the tests after every build.
While this feature didn’t really allow for real continuous testing, it was nevertheless the first step in that direction. A full solution for continuous testing was introduced in Visual Studio 2017 as a feature named Live Unit Testing.
At about the same time, a similar feature was added to the command line tools for .NET Core.
History: 2017-11-23: Update and reformatted
