VSTS - how to get Code Coverage results

问题:

I'm new to DevOps work and I've been tasked to setup a build for one of our .net Standard Library projects. I used the build template for this, which works great! But I want to add a code coverage into build output (there's a test project in the solution).

In the "VsTest - testAssemblies" task, I've checked the "Enable Code Coverage" option, as shown below:

I added a Publish code coverage task and it's asking for something called a "Summary File" - see below:

I'm not sure how to set this option? Has anyone done this?

I seem to get test results published in the build results without config, see below:

And I'd like the same for the Code Coverage tab in the build results, which is currently blank:

Also (may be a completely separate question), I was wondering - can I add a "Quality Gate" to say if Coverage is below 80% then fail the build?

Thanks for any advice in advance - it's a case of knowing what I want, but not sure how to achieve it!

回答1:

By default, the VsTest task will publish the Code Coverage result to Build Summary page directly. So we don't need Publish Code Coverage result task to publish the coverage result. Just make sure you have selected "Code Coverage enable" section in VsTest task.

>> Also (may be a completely separate question), I was wondering - can I add a "Quality Gate" to say if Coverage is below 80% then fail the build?

In current VSTS, we could not set "Quality Gate" to set the build failed if it doesn't match the configured % value. There has other communities also have this requirement and have submit a user voice. Please feel free to add your comments or vote it from below link: https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/3817520-fail-build-on-insufficient-code-coverage

回答2:

Hurrah!!! There is a solution for it. :)

You have to install a an Add-on to your organization in VSTS (Azure DevOps). The name of the addon is Build Quality Checks

Here is the link: https://marketplace.visualstudio.com/items?itemName=mspremier.BuildQualityChecks

It works perfectly. And this is what you want