This release includes the following enhancements:

Release date: May 17, 2023

Visual Studio Code Integration with Import Coverage

• dotTEST extension for VS Code now supports downloading coverage results from CI/CD pipelines (GitHub, GitLab, Azure DevOps).
• Coverage markers are automatically refreshed when coverage data is modified.
• Coverage data is visualized inside Codespaces for VS Code plugin as part of GitHub integration.

Code Coverage Enhancements

• dotTEST includes a new standalone coverage tool (dottestcov) with extended capabilities for creating coverage reports that can be easily incorporated into different testing flows.
• QA teams can now measure code coverage for their applications without needing access to source code. dottestcov can be used to scan application assemblies (PDB files are required to collect coverage) and create a report containing the scope of testable code in the application, as well as create reports containing the runtime coverage data collected by the dotTEST coverage agent. These reports can be uploaded to Parasoft DTP, which aggregates the coverage data to provide a comprehensive overview of your application’s coverage metrics.
• Teams can use the test impact analysis capability of dottestcov to calculate the specific set of tests that they must run to validate just the code that changed in a new version of their application.
• dottestcov enables simplified coverage workflows. Runtime coverage reports can now be created and uploaded to Parasoft DTP independently of the static coverage file produced by analyzing source code (see Generating the Static Coverage File with Source Code Information). Additional configuration and usability enhancements simplify workflows for setting up coverage and test impact analysis configuration for applications.
• For additional details about the new capabilities and dottestcov usage, see Application Coverage.

Support for BDD Testing

dotTEST now supports running BDD SpecFlow tests seamlessly alongside unit tests. You can now easily gather results from BDD tests and publish them to DTP.

Note: Coverage collection for SpecFlow tests is not supported yet.

New and Updated Test Configurations

The Security Compliance Pack has been extended by adding support for the following test configurations:

• CWE 4.10
• OWASP ASVS 4.0.3

Additionally, the Recommended .NET Core Rules test configuration has been renamed to Recommended .NET Rules.

Updated Static Analysis Rules

The following rule has been updated:

New and Updated Flow Analysis Rules

The following rules have been added:

The following rules have been updated:

Additional Updates

• Test Impact Analysis now supports analyzing solutions that have their sources outside of the solution root folder.
• OIDC support for Google authentication has been added.
• Support for default parameters of cloned and mapped rules defined in rulemap.xml has been added. The values are visible in the Test Configuration Editor in the IDE.
• Dark mode support has been added to Visual Studio Parasoft Plugin.
• Optimized execution time of rules in Compliance Packs and cloned rules.
• Improved support for C# lambdas in Flow Analysis.
• General improvements to the Flow Analysis engine may cause some differences in the violations reported by Flow Analysis rules compared to the previous version.

Removed Support

Removed Support for Team Server

Team Server has been removed and is no longer supported. If your team configurations, rules, and rule mappings are still stored in DTP Team Server, migrate them to a shared location. See Migrating Test Configurations, Rules and Rule Mappings from the Team Server to a Shared Location.

Removed Support for Platforms

Support for the following platform is now removed:

• Windows Server 2019

Removed Support for Development Platforms

Support for the following development platform is now removed:

• .NET Core 3.1

Deprecated Rules

Resolved Bugs and FRs