Versions Compared

Old Version 2

changes.mady.by.user Izabela Jarosz

Saved on

compared with

New Version 3

changes.mady.by.user Izabela Jarosz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Scroll Ignore
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmltrue

This release includes the following enhancements:

Table of Contents
maxLevel1

Release date: May 16, 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 Enhancement

Support for simplified coverage flows with the use of the new dottestcov tool has been introduced.

  • dottestcov is a standalone tool that can be used independently, so that you can easily incorporate it into your testing flow.
  • 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. 
  • With dottestcov you can merge previously generated runtime coverage reports and send them to DTP.
  • 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.
  • For 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.

Visual Studio Code Integration with Import Coverage

dotTEST extension for VSCode now supports downloading coverage results from CI/CD pipelines (GitHub, GitLab, Azure DevOps).

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:

Rule IDUpdates
CS.PROTCSupport for .NET 6+, the rule is available in CQA mode

New and Updated Flow Analysis Rules

The following rules have been added:

Rule IDHeader
BD.PB.INTDLAvoid data loss when converting between integer types
BD.PB.INTVCAvoid value change when converting between integer types
BD.PB.INTWRAPAvoid wraparounds when performing arithmetic integer operations

The following rules have been updated:

Rule IDUpdates
BD.EXCEPT.NRImproved performance of the rule.
BD.PB.UGHCImproved accuracy of the rule.
BD.SECURITY.SENSLOGImproved 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.
  • 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.

  • 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 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

    Deprecated RuleSuggested Rule
    BD.PB.INTOVERF BD.PB.INTWRAP, BD.PB.INTDL and BD.PB.INTVC

    Resolved Bugs and FRs

    Bug/FR IDDescription
    FA-9166BD.PB.ARRAY missing violation when array is statically initialized class variable
    FA-9261BD.PB.CC false negative when checking out-of-range value for equality
    XT-40717The same suppressions reason reported for all comment suppressions in single line
    XT-40748Incorrect behavior of "wait for tokens" option
    XT-40970Applying OIDC settings does not force authentication when refresh token is invalid
    XT-41092Relative paths to rule links are resolved to absolute making reports and rule docs non-portable

    ...