Speckit.tester
Test Runner & Coverage - Create test plans, write tests, report coverage.From its SKILL.md
npx -y skills add wedabro/bro-skills --skill speckit.testerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 330 tokens by cl100k_base, as published. Nobody here has run it
π― Mission
Make sure the implementation has full test coverage and passes 100%.
π₯ Input
- Source code (implemented files)
.agent/specs/[feature]/tasks.md(completed tasks).agent/specs/[feature]/spec.md(success criteria)
π Protocol
- Test Plan: From tasks.md (completed) β list functions/routes to test.
- Write Tests: For each function/route:
- Happy path (valid input β correct output)
- Error path (error input β error handling correct)
- Edge case (boundary values, empty, null)
- Run Tests:
docker compose exec [service] npm testor equivalent. - Coverage Report:
π Test Coverage Report βββββββββββββββββββββββ Files Tested: 12/15 (80%) Tests Passed: 45/48 (93.7%) Tests Failed: 3 βββββββββββββββββββββββ Untested: src/api/payment.ts, src/utils/cache.ts, src/hooks/useAuth.ts - List failed tests with error details.
π€ Output
- Test files (theo convention:
*.test.ts,*.spec.ts) - File:
.agent/memory/test-report.md
π« Guard Rails
- DO NOT skip error path tests β must also test failing cases.
- DON'T mock too much β prefer integration tests for API routes.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.