Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/testing-preferred-patterns
Identify and fix testing mistakes: flaky, brittle, over-mocked tests.
Passed 16 of 22 test cases with the skill, and 6 of 22 without it.
and 7 more in the full report
10 fixed6 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before flagging quality issues in `tests/e2e/login.spec.ts`, what project file should be checked for repository-specific testing conventions?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies checking `CLAUDE.md` for project testing conventions. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill identifies and fixes common testing mistakes across unit, integration, and E2E test suites. Tests should verify behavior, be reliable, run fast, and fail for the right reasons.
Scope: This skill focuses on improving test quality and reliability. It complements test-driven-development by addressing what goes wrong with tests, complementing how to write them correctly from scratch.
Out of scope: Writing new tests from scratch (use test-driven-development), fixing fundamental architectural issues (use systematic-refactoring), or profiling test performance with external tools.
| Signal | Load These Files | Why |
|---|---|---|
| BAD/GOOD code examples for all 10 testing failure modes | preferred-pattern-catalog.md | Loads detailed guidance from preferred-pattern-catalog.md. |
| auditing coverage gaps: concurrency, boundaries, security, error recovery | blind-spot-taxonomy.md | Loads detailed guidance from blind-spot-taxonomy.md. |
| errors, error handling | error-handling.md | Loads detailed guidance from error-handling.md. |
| fixing review feedback | fix-strategies.md | Loads detailed guidance from fix-strategies.md. |
| tests | load-test-scenarios.md | Loads detailed guidance from load-test-scenarios.md. |
| classifying test-quality failure modes found during SCAN | quality-catalog.md | Loads detailed guidance from quality-catalog.md. |
| fast pattern-symptom-fix lookup | quick-reference.md | Loads detailed guidance from quick-reference.md. |
Goal: Identify quality issues present in the target test code.
Step 1: Locate test files
Use Grep/Glob to find test files in the relevant area. If user pointed to specific files, start there. Common patterns:
*_test.gotest_*.py or *_test.py*.test.ts, *.spec.ts, *.test.js, *.spec.jsStep 2: Read CLAUDE.md
Check for project-specific testing conventions before flagging quality issues. Some projects intentionally deviate from general best practices. This prevents false positives based on organizational standards.
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.