Incomplete coverage report?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- next.js, react, typescript
Research direction
Reproduce the report using the Next.js 13.5.4 setup with swc-plugin-coverage-instrument and the rendered React component described in the issue. Inspect why the export is marked covered while the component is not; done means coverage accurately reflects the component render and the existing test still reports coverage correctly.
Written by the indexing model from the issue text.
Description
Hi, thanks for the library.
For some reason some React components that are part of the pages I'm testing don't result covered, here's an example.
The export is marked as covered but the component itself doesn't, but I am 100% sure the component is being rendered in the page. I tried to throw new Error("nyc") from it and the test failed with the expected error message.
I'm using Next.js 13.5.4 with swc-plugin-coverage-instrument.
Do you know what could be going on here?
- Dominant language
- TypeScript
- Stars
- 143
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
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.
More from mxschmitt/playwright-test-coverage
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Example with Remix Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mxschmitt/playwright-test-coverage#21 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mxschmitt/playwright-test-coverage#17 · 6 comments ·
All issues in mxschmitt/playwright-test-coverage
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·