Continuous Testing is the process of executing automated tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate. This practice is strongly associated to the Continuous Delivery approach. In his article “Continuous Testing in .NET”, Damir Arh proposes an overview of continuous testing and how to implement it in Visual Studio.
At the beginning of the article, Damir Arh explains that “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 be done only with the support of some tools and the article propose of list of some of the commercial tools that can be used in a .NET context. A feature named Live Unit Testing was introduced in the Enterprise edition of Visual Studio 2017 and is presented in the article.
The article describes how to setup a project that will be used for the example. Then it explains that Live Unit Testing works better when you use Test Driven Development (TDD) and write tests at the same time that you are writing the code. It also describes how to use the set of command line tools of .NET Core SDK to prepare a working environment for continuous testing. The conclusion of the article is that “Support for continuous testing is becoming more common in the .NET ecosystem and will only improve in the future. The .NET Core command line tools can be used with any editor and on any platform. Visual Studio 2017 introduces the Live Unit Testing feature, which is only included in the Enterprise edition. For other editions there are alternative third-party commercial extensions available.”
You can read the complete article “Continuous Testing in .NET” on http://www.dotnetcurry.com/aspnet/1396/continuous-testing-dotnet