No report files and directory specified errors after running dotnet tool run using ReportGenerator

Question

I am having an issue after running the 'dotnet tool run' command on step 6 of 'Run code coverage locally' within the 'Exercise—Perform code coverage testing' Azure DevOps learning path.

https://learn.microsoft.com/en-us/training/modules/run-quality-tests-build-pipeline/6-perform-code-coverage

This question is related to the following Learning Module

Answer 1

Hi BRAY, MATTHEW,

Thank you for reaching out to us through the Microsoft Q&A forum. 

We understand that you are encountering the "No report files and directory specified" error while executing the dotnet tool run command for ReportGenerator. This issue typically arises when the specified report file path is incorrect or when the report file does not exist at the designated location. 

To assist you in troubleshooting this issue, please consider the following steps: 

1.Verify the Path: Ensure that the path to the Cobertura file (coverage.cobertura.xml) provided in your command is accurate. It is essential to confirm that the file exists in the specified directory: 

-reports:./Tailspin.SpaceGame.Web.Tests/TestResults/Coverage/coverage.cobertura.xml

2.Check Build Output: Please verify that the prior command to execute the unit tests and generate the Cobertura report was successful. Confirm that the report file was created in the specified directory by examining the output folder. 

3.Execute the Command Manually: Sometimes, executing the command manually can help identify specific issues: 

dotnet tool run reportgenerator -- -reports:./Tailspin.SpaceGame.Web.Tests/TestResults/Coverage/coverage.cobertura.xml -targetdir:./CodeCoverage -reporttypes:HtmlInline_AzurePipelines

4.Examine Directory Permissions: Ensure that you possess the necessary permissions to read from the input directory and to write to the output directory. 

5.Consider an Alternative Format: If the issue continues, you may want to attempt running ReportGenerator with a different report format or output location to determine if that resolves the problem. 

If you have any additional questions, please do not hesitate to contact us. 

Should you find this information helpful, kindly acknowledge by selecting "Accept Answer" and upvoting the response.