13

Exclude automatic properties from code coverage in Visual Studio 2015

 3 years ago
source link: https://www.codesd.com/item/exclude-automatic-properties-from-code-coverage-in-visual-studio-2015.html
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Exclude automatic properties from code coverage in Visual Studio 2015

advertisements

I just upgraded a bunch of projects to VS2015/C#6.

Now MSTest's Code Coverage analysis is reporting that some auto properties aren't covered by unit tests. This wasn't the case in Visual Studio 2013, and I suspect it may be something to do with the new autoproperty features in C#6.

Dealing with all the false-positives this generates rather defeats the purpose of the Code Coverage tool as it makes it practically impossible to identify actual code lacking test coverage. We don't want to write unit tests for all our DTOs, and I'd really rather not have to go through the project annotating every single auto-property with ExcludeFromCodeCoverage.

I've created a working MCVE at https://github.com/iaingalloway/VisualStudioCodeCoverageIssue

  • Open VisualStudio2013.sln in Visual Studio 2013 Premium or Ultimate.
  • Click Test -> Analyze Code Coverage -> All Tests.
  • Observe that the "Code Coverage Results" window reports 0 Blocks "Not Covered".
  • Open VisualStudio2015.sln in Visual Studio 2015 Enterprise.
  • Click Test -> Analyze Code Coverage -> All Tests.
  • Observe that the "Code Coverage Results" window reports 1 Block "Not Covered" (the getter for ExampleDto.Value)

Is it possible to configure the built-in Code Coverage tool in Visual Studio 2015 to ignore auto-properties like Visual Studio 2013 does?

As a workaround, you can add the following to your .runsettings file:-

<RunSettings>
  <DataCollectionRunSettings>
    <DataCollector ...>
      <Configuration>
        <CodeCoverage>
          <Functions>
            <Exclude>
              <Function>.*get_.*</Function>
              <Function>.*set_.*</Function>
            </Exclude>
          ...

It's not a great workaround, but as long as you aren't using any functions with "get_" or "set_" in the names it should get you the behaviour you need.


report

Recommend

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK