This blog has solutions to 2 problem statements:
The second problem statement is a hot topic in the developer community as many developers want to publish Jmeter Reports(Or any other report) within Azure Devops. See below link:
We have created a custom extension which solves the problem of sending Jmeter (Or any) HTML report to azure devops. …
Rendering code coverage reports on Sonarqube and Azure Devops is a common expectation while we are creating CI pipelines.
Although, its very easy to publish code coverage reports on azure devops using “PublishCodeCoverageResults@1” task, but there is a limitation here of azure devops, it cannot publish opencover.xml code coverage reports.
Also, Sonarqube doesn't support Cobertura code coverage reports.
So, how do you publish the code coverage reports on both azdo and Sonarqube.
One way to do this is:
100 percent code coverage!! Well thats what we keep hearing from our colleagues and we all aspire for 100 percent code coverage but somewhere deep within ourselves we know that sometimes writing unit test cases for an application takes more time than the actual implementation of business logic!! If at all, 100 percent code coverage was that easy, all our projects would have had the perfect score.
We were writing azure functions and our business logic was dependant on azure-storage accounts- table, blob and queue storage. We had a lot of calls to the storage accounts and to ensure that…