ReneSchumacher
commented
1 year ago Hi @seshadrimr,
if you're using SonarQube, you could create a code coverage quality gate in there as well, so you don't need the Build Quality Checks task just to check a code coverage threshold. For more complex scenarios like comparing with previous builds, I guess BQC is needed, but I'm not that familiar with all the quality gates in SonarQube.
Afaik, the .NET Core task may not publish code coverage data to Azure DevOps. Can you please check if you see coverage values on the build summary page like this:
If not, please check if the option to publish test results and code coverage is checked in the test task:
kieseldlds
Hi. I created a DevOps starter project on Azure DevOps. Brought in a simple .Net core WebApi with Unit test. I wanted to break the build if the code coverage is lesser than a configurable value. Hence I added 'Build quality check' task after the .Net Core 'Test' task. It validates the code configuration policy and always says 'Waiting for Code Coverage data'. It breaks since the Maximum timeout reaches. Am I missing some setting here? From where does the task look for the Code coverage data? I also have 'Prepare code analysis' for SonarCloud task. The code coverage data gets reflected in SOnarCloud. I added the argument '--collect "Code coverage"' in the 'Test' task.
Please guide me in this problem. Attached the pipeline steps.