// //

Want to see Parasoft in action? Sign up for our Monthly Demos! See Demos & Events >>

X
.NET Structural Code Coverage

C# and VB.NET Code Coverage

Powered by Parasoft dotTEST

Code Coverage for C# and VB.NET

Parasoft’s solution for code coverage provides critical feedback about the completeness and thoroughness of the testing process, which is an absolute must-have for any organization where the high-quality of the source code matters by correlating tests with code coverage results.

How Does It Work?

Parasoft dotTEST’s code coverage solution for .NET enables users to collect coverage from unit testing from all of the .NET Framework versions starting with .NET Framework 2.0, as well as .NET Core starting with version 2.0. It executes and collects coverage from the most popular testing frameworks (.NET Core, NUnit 2, MSTest, since 10.4.0: NUnit 3, MSTest V2, and xUnit).

Parasoft dotTEST also enables users to monitor standalone or web applications and collect code coverage from code that was executed in an application run. This functionality enables QAs and testers to collect coverage from their manual or automated tests, and it is easy to set up for an automated process, integrating seamlessly with Parasoft SOAtest as well as third-party test execution software.

Both approaches provide rich test traceability, making it easy to track covered code per test which can be really useful when a customer wants to check what is tested by his test case or to e.g. provide proper isolation for his unit tests (if the test is executing unwanted code which is e.g. accessing some files in local storage or modifying environment, customer can stub or mock it).

Parasoft includes intelligent insights in the reporting process about the relationship of code coverage results to the test cases.

Features

Parasoft’s solution for requirements traceability helps you harness the relationship between all important artifacts in the development process. With Parasoft’s centralized reporting dashboard, you can see the correlation between requirements and the following:

  • Source code created to implement requirements.
  • Test cases created to test the requirements.
  • The source code exercised by the specific individual test cases.
  • Results of executed tests and code coverage results.

Traceability reports provide clear and complete information about the development progress, and teams can easily determine how many requirements were already implemented and how thoroughly they have been tested.

Unit tests that are executed by dotTEST can be correlated to requirements. Parasoft automatically captures the results of the test case execution with the information about the code coverage generated during specific test execution.

Parasoft’s reporting module for requirements traceability can be integrated with any RMS. This flexible connector for interfacing with the Requirements Management Systems supports not only the most advanced and popular Requirements Management Systems, but also smaller and less popular solutions on the market.

Parasoft dotTEST can be used to instrument an entire application’s code base for code coverage monitoring. The instrumented application can be executed and examined based on the test procedures defined in manual test scenarios. During testing, users can annotate the coverage results with the information about the executed test scenarios. The coverage results collected from the testing process are shown in Parasoft’s centralized reporting dashboard, which provides a unique ability to generate merged unit testing and system testing coverage results. Merged reports help in determining the quality of the testing process and help in focusing and optimizing the testing effort.

Benefit From the Parasoft Approach

Get the traceability needed to meet compliance requirements

To eliminate manual effort associated with demonstrating compliance, users can automatically correlate test results and coverage with requirements. This enables users to easily produce the documentation required for standards and guidelines such as FDA, ISO 26262, and DO-178B/C.

Easily understand the impact of code changes

To reduce the time required to test the software project by removing redundancy in testing, Parasoft dotTEST users can take advantage of Parasoft’s test impact analysis technology in its centralized reporting server to identify specific test cases that can be re-run to test code changes.

Aggregate data from across all of testing to correlate with requirements

By taking data from multiple testing practices and correlating it with requirements in Parasoft’s centralized reporting and analytics system, users get immediate feedback about the quality of business requirements.