testing-process
Testing & Quality Assurance Process
Guidelines
- Always try to add tests for any new functionality, and make sure to cover all cases and code branches, according to requirements.
- Always try to add tests for any bug-fixes, if the discovered bug is not already covered by tests. If the bug was already covered by tests, fix the existing tests as needed.
- Always run all existing tests after you are done with a given implementation or bug-fix.
Use the following guidelines when working with tests:
- Ensure comprehensive testing
- Use table-/data-driven tests and test generation
- Benchmark tests and performance regression detection
- Integration testing with test containers
- Mock generation with %LANGUAGE% best practices and well-establised %LANGUAGE% mocking tools
- Property-based testing with %LANGUAGE% best practices and well-establised %LANGUAGE% testing tools
- Propose end-to-end testing strategies if automated e2e testing is not feasible
- Code coverage analysis and reporting
More from serpro69/claude-toolbox
cove
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
1merge-docs
Semantically compare and merge two design docs for the same feature into one unified document. Use when you have two competing or complementary design/implementation docs (e.g., from separate analysis-process runs) and need to reconcile them into a single source of truth.
1analysis-process
Turn the idea for a feature into a fully-formed PRD/design/specification and implementation-plan. Use when you have a spec or requirements that needs implementation. Use in pre-implementation (idea-to-design) stages to make sure you understand the spec/requirements and ensure you have a correct implementation plan before writing actual code.
1documentation-process
After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix
1solid-code-review
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
1development-guidelines
Use when writing code to ensure you follow development best practices during development and implementation.
1