This release includes the following enhancements: Release date: May 1617, 2023 Visual Studio Code Integration with Import Coverage EnhancementSupport for simplified coverage flows with the use of the new dottestcov tool has been introduced. - 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 dottestcov offers extended capabilities for creating coverage reports . Coverage reports can now be generated and uploaded to DTP based on scans of application binaries and runtime data collected during application runs. Runtime reports can be appended to existing coverage data on DTP, providing a comprehensive overview of your application's coverage metrics. This enables simplified workflows, e.g. QA testing where coverage can be collected and measured without access to source code.
- The easy configuration and usability enhancement simplifies workflows for setting up coverage and TIA configuration for applications.
- With dottestcov you can merge previously generated runtime coverage reports and send them to DTP.
- dottestcov is a standalone tool that can be used independently, so that you can easily incorporate it into your testing flow.
- 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 For details about the new capabilities and dottestcov usage, see Application Coverage.
Support for BDD TestingdotTEST 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. Visual Studio Code Integration with Import CoveragedotTEST extension for VSCode now supports downloading coverage results from CI/CD pipelines (GitHub, GitLab, Azure DevOps). New and Updated Test ConfigurationsThe Security Compliance Pack has been extended by adding support for the following test configurations: Additionally, the Recommended .NET Core Rules test configuration has been renamed to Recommended .NET Rules. Updated Static Analysis RulesThe following rule has been updated: | Rule ID | Updates |
|---|
| CS.PROTC | Support for .NET 6+, the rule is available in CQA mode |
New and Updated Flow Analysis RulesThe following rules have been added: | Rule ID | Header |
|---|
| BD.PB.INTDL | Avoid data loss when converting between integer types | | BD.PB.INTVC | Avoid value change when converting between integer types | | BD.PB.INTWRAP | Avoid wraparounds when performing arithmetic integer operations |
The following rules have been updated: | Rule ID | Updates |
|---|
| BD.EXCEPT.NR | Improved performance of the rule. | | BD.PB.UGHC | Improved accuracy of the rule. | | BD.SECURITY.SENSLOG | Improved performance of the rule. |
Additional Updates- Dark mode support has been added to Visual Studio Parasoft Plugin.
- 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.
Removed SupportRemoved Support for Team ServerTeam 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. 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 SupportSupport for the following platform is now removed: Support for the following development platform is now removed: Deprecated Rules| Deprecated Rule | Suggested Rule |
|---|
| BD.PB.INTOVERF | BD.PB.INTWRAP, BD.PB.INTDL and BD.PB.INTVC |
Resolved Bugs and FRs| Bug/FR ID | Description |
|---|
| FA-9166 | BD.PB.ARRAY missing violation when array is statically initialized class variable | | FA-9261 | BD.PB.CC false negative when checking out-of-range value for equality | | XT-40717 | The same suppressions reason reported for all comment suppressions in single line | | XT-40748 | Incorrect behavior of "wait for tokens" option | | XT-40970 | Applying OIDC settings does not force authentication when refresh token is invalid | | XT-41092 | Relative paths to rule links are resolved to absolute making reports and rule docs non-portable |
|