aktonay/skillz / skills/development/test
test
UnverifiedGenerate comprehensive tests for code and features. Use when writing new tests or improving test coverage for a behavior, bug fix, or regression.
Write Tests
When writing tests, follow these guidelines:
- Cover the happy path first.
- Cover edge cases, including empty inputs and boundary values.
- Cover error paths.
- Use one assertion per test where possible.
- Prefer descriptive test names.
- Test behavior, not implementation details.
- Use realistic test data.
- Mock external dependencies like network, database, and filesystem.
Preferred test structure:
describe('<ComponentOrFunction>', () => {
it('<expected behaviour> when <condition>', () => {
// Arrange
// Act
// Assert
})
})
Aim for at least 1 happy path, 2 edge cases, and 1 error case per function.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |