VS 2012 introduces a new and simplified code coverage experience. Now we instrument native and managed binaries (DLLs\/EXEs) as they are loaded at runtime as long as these binaries are a part of your solution, and get called by any of your test cases under execution. In contrast, you had to specify your target dlls in your .testsettings file in VS 2010.<\/p>\n
For advanced users we allow customization of our selection logic using the .runsettings file. For mode details see our blog post \u201cCustomizing Code Coverage in Visual Studio 11<\/a>\u201d<\/p>\n \u00a0<\/p>\n 2. Support in Visual Studio\u2019s Test Explorer window<\/strong><\/span><\/p>\n With this prominent menu item in your Test Explorer window you can now run your tests and get code coverage data all at once, by just clicking the \u201cAnalyze Code Coverage for All Tests\u201d instead of the \u201cRun All\u201d item. With minimal execution time overhead this will run all your tests and display the code coverage results immediately after the run is completed.<\/p>\n You get a similar menu item for code coverage when you select and run a subset of your unit tests from the Test Explorer window.<\/p>\n \u00a0<\/p>\n 3. Native is a first class citizen<\/strong><\/span><\/p>\n Yay! With the introduction of the Native Unit Test project in VS 2012 we have enabled code coverage for native code as well. Now you no longer need to move to the command line when you want coverage data for native applications. The experience remains exactly the same whether you are working with managed code or native code. What\u2019s more – mixed solutions work just as well.<\/p>\n \u00a0<\/p>\n 4. The .coverage file is leaner and meaner<\/strong><\/span><\/p>\n You want to share your .coverage file? Go ahead and share the file \u2013 and only the .coverage file. In VS 2012 the .coverage file is self-contained and we have tried to ensure that we keep the size to the very bare minimum even with this additional data. So no more copying of instrumented binaries with the .coverage file for it to open up in Visual Studio.<\/p>\n \u00a0<\/p>\n 5. Support in the new test executor command line<\/strong><\/span><\/p>\n The new unit test executor vstest.console.exe supports code coverage with a simple addition of the \u201c\/enablecodecoverage\u201d switch. Append this switch to the command line arguments used for your test run and you get code coverage data as well.<\/p>\n \u00a0<\/p>\n 6. Support in Team Build<\/strong><\/span><\/p>\n Enabling code coverage on your build definition is as simple as selecting the \u201cEnable Code Coverage\u201d item in the options combo box when you specify your test dll to be run. And yes, this works on your Team Foundation Service too.<\/p>\n Note: This is available only when you select the \u201cVisual Studio Test Runner\u201d<\/em><\/p>\n 7. Support for .net\/cpp custom unit test adapters<\/strong><\/span><\/p>\n As you all know the unit testing framework is now extensible and supports custom test adapters. The xunit, nunit folks have their adapters available via the Visual Studio Extensions gallery already and code coverage is functional on these test adapters. We would work for any custom adapter that deals with .net (managed) or cpp (native) code. Caveat: If the adapter is doing any runtime magic e.g. using the .net profiler interfaces for some reason, code coverage would not be supported.<\/p>\n Note: Other languages are not supported for code coverage<\/em><\/p>\n \u00a0<\/p>\n While making all the above changes we have ensured that your interaction with the .coverage file is exactly the same as VS 2010 – through the Code Coverage Results window. We continue to report block and line coverage data.<\/p>\n We surely hope that the above changes have helped alleviate the pains of getting started and working with code coverage in this Agile world.<\/p>\n \u00a0<\/p>\n Resources:<\/p>\n a) MSDN: Using Code Coverage to Determine How Much Code is being Tested<\/a><\/p>\n b) Troubleshooting missing data in Code Coverage Results<\/a><\/p>\n c) Visual Studio UserVoice<\/a><\/p>\n![\"clip_image001\"](\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2012\/06\/1200.clip_image001_thumb_3E76B2A8.png\" "\\"clip_image001\\"")
<\/p>\n![\"clip_image002\"](\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2012\/06\/0218.clip_image002_thumb_40EFBE99.png\" "\\"clip_image002\\"")
<\/p>\n