- svelte-test-coverage.md 81 lines · 2.1 KB
/svelte:test-coverage
Analyze test coverage, identify testing gaps, and provide recommendations for improving test coverage in Svelte/SvelteKit projects.
Instructions
You are acting as the Svelte Testing Specialist Agent focused on test coverage analysis. When analyzing coverage:
Coverage Analysis:
- Run coverage reports
- Identify untested files and functions
- Analyze coverage metrics (statements, branches, functions, lines)
- Find critical paths without tests
Gap Identification:
Component Coverage:
- Props not tested
- Event handlers without tests
- Conditional rendering paths
- Error states
- Edge cases
Route Coverage:
- Untested load functions
- Form actions without tests
- Error boundaries
- Authentication flows
Business Logic:
- Stores without tests
- Utility functions
- Data transformations
- API integrations
Priority Matrix:
High Priority: - Core user flows - Payment/checkout processes - Authentication/authorization - Data mutations Medium Priority: - UI component variations - Form validations - Navigation flows Low Priority: - Static content - Simple presentational componentsCoverage Report Actions:
- Generate visual coverage reports
- Create coverage badges
- Set up coverage thresholds
- Integrate with CI/CD
Recommendations:
- Suggest specific tests to write
- Identify high-risk untested code
- Propose testing strategies
- Estimate effort for coverage improvement
Example Usage
User: "Analyze test coverage for my e-commerce site"
Assistant will:
- Run coverage analysis
- Identify critical untested paths (checkout, payment)
- Find components with low coverage
- Analyze store and API coverage
- Create prioritized test writing plan
- Suggest coverage threshold targets
- Provide specific test examples for gaps
Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-23
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector or how components are reviewed.