Running coverage locally shows empty coverage report
- Dominant language
- JavaScript
- Stars
- 15.7k
- Forks
- 3.9k
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 34
Description
As tested on 9b986ab79a00d9a0119985142362f45e4eb8e27c on the `main` branch, in a clean repository, ran the following commands:
```bash
npm install
npm run build
npm run coverage
```
The terminal log showed that all the tests ran and that that `coverage` task completed in 2 minutes, however, the report opened up as empty:
This does not seem to be a problem [in CI](http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/main/Build/Coverage/Firefox%20103.0%20(Linux%20x86_64)/index.html).
Contributor guide
Research direction
Reproduce the issue in a clean repository with npm install, npm run build, and npm run coverage. Then inspect the coverage task and compare the local report with the CI coverage report linked in the issue. Done means the local report contains coverage data instead of opening empty.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100