Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This and all the following analysis types are performed with a built-in or user-defined test configuration; see Configuring Test Configurations.

0A01020401598D973E684FA84B2F8FAC
Info
iconfalse
titleSupport .NET Core Projects

dotTEST can perform pattern-based analysis on .NET Core projects, but some rules are not supported. See .NET Core Supported Rules for the list of rules that are available when you run analysis on .NET Core projects.

Conditional Content
product: (dottest)product: (dottest)sv-attr:0A01020401598D973E6641760F8AF4E5

Info
iconfalse
titleRunning Microsoft Code Analysis in dotTEST

You can run Microsoft Code Analysis rules with dotTEST - using the standard dotTEST static analysis workflow and reporting capabilities.  This requires one of the following to be installed on your machine:

  • Visual Studio 2013, 2015, or
2017 to be installed on your machine
  • 2017
  • Build Tools for Visual Studio 2017 with the "Static analysis tools" option enabled

Microsoft Code Analysis is not supported for .NET Core projects.

Code Duplication Analysis

...

dotTEST

can dotTESTcan check for duplicate code to help you improve application design and decrease maintenance costs. During code duplication analysis, the code is parsed into smaller language elements (tokens). The tokens are analyzed according to a set of rules that specify what should be considered duplicate code. There are two types of rules for analyzing tokens:

...

Code Block
builtin://Find Duplicated Code

Metrics Analysis

...

dotTEST

can dotTESTcan compute several code metrics, such as code complexity, coupling between objects, or lack of cohesion, which can help you understand potential weak points in the code. Run the Metrics test configuration during analysis to execute metrics analysis rules: 

...

  • By using the test configuration interface in DTP (see "Report Center> Test Configurations> Editing Test Configurations> Metrics Tab" in the Development Testing Platform DTP user manual for details).
  • By editing the Metrics test configuration using the interface in an IDE (see Creating Custom Test Configurations).
  • By manually editing the test configuration file:

    1. Duplicate the built-in Metrics test configuration ([INSTALL_DIR]/configs/builtin) to the user configurations directory ([INSTALL_DIR]/configs/user).

    2. Open the duplicate configuration in an editor and set the [METRIC.ID].ThresholdEnabled property to true.

    3. Configure the lower and upper boundaries in the [METRIC.ID].Threshold property according to the following format: [METRIC.ID].Threshold=l [lower boundary value] g [upper boundary value]

    4. Save the test configuration and run the analysis using the custom metrics test configuration.

...