Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jamestorrevillas/testing
Use this skill when writing or improving tests of any kind — unit tests, integration tests, end-to-end (E2E) tests, API tests, or test coverage analysis. Trigger on keywords: test, spec, unit test, integration test, E2E, Playwright, Jest, Vitest, pytest, mock, coverage, TDD, test suite, assertion.
Passed 22 of 22 test cases with the skill, and 20 of 22 without it.
2 fixed20 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
When prioritizing test coverage for unit test scenarios (happy path, edge cases, error paths, invalid inputs, and performance-critical paths), what priority level is assigned to performance-critical paths?
| Checked | Without skill | With skill |
|---|---|---|
| Classifies performance-critical paths as nice to have rather than must have. | Missed | Passed |
The instructions your model reads when the skill loads.
AI-generated code is untrusted until it passes a human-reviewed test suite. Tests are not optional — they are the safety net that makes refactoring and agentic code generation safe. Treat test code with the same quality standards as production code.
The Verify Output Principle: Every piece of AI-generated code should pass through an AI-generated but human-reviewed test suite before being considered complete.
/\
/E2E\ ← Few, slow, high confidence
/------\
/Integr. \ ← Some, medium speed
/------------\
/ Unit Tests \ ← Many, fast, isolated
/------------------\
describe('ComponentOrFunction', () => {
test cases passed, vs 20 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.