Generate Report for nodejs code coverage
See original GitHub issueHello,
I am trying to generate report from cobertura coverage for a nodejs app. But, I am getting the following error:
##[error]Unable to locate executable file: 'dotnet'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
This is on Azure DevOps pipeline Parameters:
Reports: <path/to>/cobertura-coverage.xml
Target Dir: coveragereport
Report types: HtmlInline_AzurePipelines;Cobertura
Any suggestion on how to fix this?
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
How do I generate code coverage for some Node.JS ...
I have a build/ folder that gets autogenerated by a babel process in a package.json . It has several .js files, including in...
Read more >Running tests and creating code coverage reports for React ...
Running tests and creating code coverage reports for React / NodeJS project continuously with Jenkins Pipelines, Jest & Cobertura or Jest-JUnit and push...
Read more >Introduction to the Node.js reference architecture, Part 7
Code coverage can be generated easily too: Just call the nyc module in conjunction with our test to generate the coverage report.
Read more >Getting Started with Code Coverage for Javascript
Codecov is a code coverage tool that provides reports on how much of a project's codebase is tested. It is often used in...
Read more >Create Your Own Code Coverage Tool with JavaScript, Node ...
Get ready to roll up your sleeves and build your very own code coverage tool from scratch! In this video, you'll learn how...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@danielpalme Report works now. Thank you so much for the update!
The latest release now supports handling those invalid files: https://www.nuget.org/packages/ReportGenerator/4.0.12
The Azure DevOps extension is also updated. So your build should work now (it may take some time until the new version is used in your build, version number is: 1.0.21)