infrastructure: check coverage for source instead of generated JS
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.1k
- Forks
- 773
- PR merge metrics
- No merged PRs in 30d
Description
We better to check coverage for source file (.ts) instead for the JS file, to
- make it easier to see which part of code is not covered.
- remove generated file fixup https://github.com/jquery/esprima/blob/master/tools/fixupbundle.js
This could be done by source-map and https://www.npmjs.com/package/remap-istanbul.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how coverage currently targets generated JavaScript and how tools/fixupbundle.js is involved. Investigate source maps and remap-istanbul as suggested; the work is done when coverage reports point to the TypeScript source and the generated-file fixup is no longer needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- build-system, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100