Here are the known limitations of Parasoft dotTEST:

Code Analysis Rules

  • Some coding standard rules do not support x64 Assemblies.
  • The following rules will not report a violation if the violation occurs within a record or record struct in C#10 code:
    • CS.BRM.RFINE
    • CS.CMUG.PRU.FSPP
    • CS.MLC
    • CS.OOM.MI
    • CS.PE.VFFP
    • CS.PFEL
    • CS.PROTC
    • CS.SC
    • CS.SERIAL.IIDC
    • CS.SERIAL.SOIS
    • CS.SERIAL.UIS
    • CS.USO

Unit Testing

  • Due to the MSTest framework limitations, results of MSTest parameterized tests executed with VSTest are accumulated and reported as a single test.

  • VStest adapters fail to provide information about source code location when the full format of PDB files is selected in .NET. As a result:
    - Test execution with dotTEST can only be applied to the entire assembly (running tests on selected files is not available).
    - dotTEST reports may include information about projects that are "unknown".

Collecting Coverage

Static coverage will be collected for all supported file formats, while dynamic coverage will only be reported for files in the .cs or .vb format. In cases where static coverage is collected from files other than .cs or .vb, achieving 100% coverage may not be possible.

Calculating Metrics

dotTEST cannot calculate metrics for websites written in mixed C# and VB code.

LLM Integration

LLM integration does not support the CDD and METRIC rules, as well as .xml files. The Generate Suggested Fix for [rule] option is not available for these items; see Generating a Suggested Fix.

Razor and Blazor Files Support

To analyze Razor and Blazor files (files with the .cshtml, .razor and .vbhtml extensions) you need to use .NET 5.0 SDK or later. Also, the analyzed project must target .NET 5.0 or later framework.

Other

  • The Universal Windows Apps project types in Visual Studio 2017 and later is not fully supported. Nuget dependencies that are stored in the project.json file are not resolved during analysis, which may impact results.
  • Analyzing Visual Basic projects with dotTEST requires that the "Strict" and "Explicit" options be enabled in the VB project under test. Disabling any of these options may impact the accuracy of analysis results.
  • If the tested solution includes a project(s) whose solution-relative path contains the double-dot notation (/../), static analysis results reported by dotTEST 2021.2 may be inconsistent with the results reported by previous dotTEST versions. If this occurs, please contact Parasoft Support.
  • If there are whitespaces around symbol names in Conditional compilation symbols defined in Visual Studio for the tested project (e.g. "OPTION1, OPTION2" or "DEBUG ; TRACE"), Flow Analysis rules may not report violations. To workaround the issue, remove the whitespaces (e.g. "OPTION1,OPTION2" or "DEBUG;TRACE") in the Conditional compilation symbols field.

See Application Coverage for Web Applications for limitations for collecting coverage from web applications.


  • No labels

Need assistance? Visit our support page