projectwallace / projectwallace/css-code-coverage
add option to calculate coverage per input JSON
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
For my use case each JSON file represents a page, or more specifically: a page tested in a Playwright test. I'd like to know and validate the individual coverage of each file. The current setup combines the JSON input as much as possible to then calculate combined coverage. I propose to add an option to skip this 'merge-all-together' step and somehow create coverage data per JSON input file.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named in the issue. Start by tracing how the current setup merges JSON inputs and produces combined coverage, then determine where an option can preserve per-file results. Done means Playwright-generated JSON inputs can be processed without merging and individual coverage data is produced for each input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100