oxidecomputer / oxidecomputer/console
Measure code coverage of Playwright tests
Open
Nobody has claimed this yet.
tools
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
It seems like it’s not very hard to do. I had kind of dismissed code coverage as not useful but something clicked for me and I’m very curious what our coverage looks like. If it turns out it’s not useful, that’s perfectly fine. We’ve done OK without it.
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 reviewing the linked playwright-test-coverage project and the repository's Playwright test setup. Determine how coverage could be measured and whether the result is useful; done means the approach is integrated or documented with a clear assessment of its usefulness.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright, typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100