Skill

testing-process

Guides adding tests for new features/bug fixes, running all tests, and using strategies like data-driven, benchmarking, integration, mocks, property-based testing, and coverage analysis after code changes.

testing

code-quality

From kk

Install

Run in your terminal

npx claudepluginhub serpro69/claude-toolbox --plugin kk

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

finishing-a-development-branch

Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.

superpowers

134.2k

Stats

Parent Repo Stars78

Parent Repo Forks11

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Testing & Quality Assurance Process

For capy knowledge base conventions, see capy-knowledge-protocol.md.

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.

Capy search: Before applying test guidelines, search kk:test-patterns for project-specific testing approaches and known edge cases.

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

Capy index: If a novel testing approach or tricky edge case was discovered during this session, index it as kk:test-patterns.