> User Documentation Home

User Handbook
Tutorials
Resources

The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

DotCover

View this plugin on the Plugins site

dotcover: Generate code coverage data and report(s)

Executes tests and generates code coverage data and reports. The coverage data and reports are not archived for you. You need to do this as a separate step.

  • NDependXmlReportPath (optional)
    • Type: String
  • coverageAssemblyInclude (optional)
    • Type: String
  • coverageClassInclude (optional)

    Includes the specified classes for which coverage data will be generated.

    For an in-depth explanation of how filtering is applied, please see the DotCover documentation

    • Type: String
  • coverageExclude (optional)

    Excludes the specified assemblies from coverage data. Note, that in addition to this exclusion definition, the assemblies matched by the glob in the global tool configuration for DotCover (named mandatory excludes) will ALWAYS be appended.

    For an in-depth explanation of how filtering is applied, please see the DotCover documentation

    • Type: String
  • coverageFunctionInclude (optional)

    Semicolon-separated list of names of methods to include in the coverage.

    For an in-depth explanation of how filtering is applied, please see the DotCover documentation

    • Type: String
  • detailedXMLReportPath (optional)

    Set the path to the detailed XML report with coverage data that DotCover will generate. The default is unset in which case DotCover will not generate this report.

    • Type: String
  • htmlReportPath (optional)

    Path to the HTML report with coverage data that DotCover will generate. The default path is 'index.html'. This setting will have DotCover produce an index.html in the workspace + a subfolder with the data used in this webpage.

    • Type: String
  • outputDir (optional)
    • Type: String
  • processExclude (optional)

    Semicolon-separated list of process names. These processes will be disregarded in the test execution when DotCover is gathering coverage data. This can be helpful in scenarios where it is necessary to strictly define the scope of executables that are part of a test. For instance, DotCover sometimes (mistakenly) detects a database server as part of the the code being exercised in the test run, which can case problems with the coverage data because it tries to include the DB server in the scope of the test. For an in-depth explanation of how filtering is applied, please see the DotCover documentation

    • Type: String
  • processInclude (optional)

    Semicolon-separated list of process names. These processes will be considered in scope for the test execution when DotCover is gathering coverage data. This is helpful when it is necessary to restrict what executables are part of a test. For an in-depth explanation of how filtering is applied, please see the DotCover documentation

    • Type: String
  • vsTestArgs (optional)

    Additional arguments to pass to the VsTest test runner. These are simply passed through to the runner, so take care to quote them properly!

    • Type: String
  • vsTestAssemblyFilter (optional)

    A glob that picks the test assemblies to include when gathering coverage data. The default value is **/*Test/bin/**/Release/*Test.dll

    • Type: String
  • vsTestCaseFilter (optional)

    The testcase filter to pass to vstest. See this page for in-depth explanation of vstest parameters.

    • Type: String
  • vsTestPlatform (optional)

    The platform that is targeted by the tests when run through the test runner. Currently x86, x64 and ARM are supported.

    • Type: String

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

    


See existing feedback here.