Known Limitations

Here are the known limitations of Parasoft dotTEST:

• The Universal Windows Apps project types in Visual Studio 2015 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.
• 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
• Calculating metrics on machines without Visual Studio 2015 may require "Microsoft Build Tools 2015" which can be downloaded from https://www.microsoft.com/en-us/download/details.aspx?id=48159.
• dotTEST cannot calculate metrics for websites written in mixed C# and VB code.
  
• 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 Core 3.x or .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".

• 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.
• 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 Core 3.0, 3.1 or .NET 5.0 or later framework.

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