Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dokhacgiakhoa/testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
Passed 23 of 24 test cases with the skill, and 22 of 24 without it.
1 fixed22 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
I'm setting up an automated test strategy for a new microservice backend. How should I divide my efforts and tests across different testing tiers like unit, integration, and end-to-end testing to ensure high reliability without slow builds?
| Checked | Without skill | With skill |
|---|---|---|
| recommends placing the largest number of tests at the unit tier | Missed | Passed |
| recommends reserving end-to-end tests for a small number of critical flows | Passed | Passed |
The instructions your model reads when the skill loads.
Principles for reliable test suites.
/\ E2E (Few)
/ \ Critical flows
/----\
/ \ Integration (Some)
/--------\ API, DB queries
/ \
/------------\ Unit (Many)
Functions, classes
| Step | Purpose |
|---|---|
| Arrange | Set up test data |
| Act | Execute code under test |
| Assert | Verify outcome |
test cases passed, vs 22 / 24 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.