I don't understand that why code coverage is analyzing unit test assemblies,as you can see also in linked video.I think it make sense to check coverage for production code but not for the unit test assemblies, Please tell us if this is a bug in VS2013 or some other reason.

I found about runsettings but switching from testsettings would ignore testsettings' deployment (where i can specify test data files and directories to deploy in addition to the target assemblies).ExcludeFromCodeCoverage attribute would be nice for new projects but what about projects migrating from VS2010

Remove this comment

Remove this thread

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums, or
Contact Us and let us know.