Considering that the success of an application depends on the reliability of the end product and that the source code behind it is often modified, developers need a good way to ensure that no bugs make their way into the code when new lines are added. This is where code coverage tools, such as
can make a difference, as they can help determine how much code is actually executed when running automated testing tools.
According to the developer, the tool should work fine with most testing tools. However, there should be some issues with the apps compiled against any version of .NET Framework or .NET Core, the latter problems resulting from the way -oldstyle command switch works in general.
There are several advantages to using a code coverage application to measure the code objects, starting with the fact that it can help determine the parts of the code that are covered or not covered by the tests. Based on the results, developers can decide whether a chunk of code needs more testing or perhaps, decide to create specific tests for the parts that are not tested and hence, could cover bugs. Needless to say, developers can also simply decide to remove the parts of the code that are unexecuted.