On Tuesday, September 23, 2014 1:28:04 PM UTC-5, Jeff Dege wrote: > > What does the "Enable Code Coverage" option, for VsTestRunner actually do? > > We want to include code coverage reports in our Jenkins builds. We've > upgraded VS2013 on our build machine from Professional to Premium, so VS's > code coverage tools are available. We've checked the "Enable Code > Coverage" option, in our VsTestRunner configuration. > > Jenkins doesn't seem to have a plug-in for viewing VsTest XML output, so > we're running an xlst on the output to create a JUnit xml file, which we > publish using the Junit test result report. > > It seems more complex than is necessary, but it's been working. > > But how to include code coverage reports? > > What does VsTestRunner output, for code coverage, when we select "Enable > Code Coverage"? And how do we get it to display with the build? > > OK, I figured out what the option does. If I check it, I see a *.coverage files, sitting in a guid subdirectory under TestResults. It's a binary file, and I know it's not being processed by our xslt.
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
