Testing Strategies
Comprehensive testing strategy covering unit, integration, e2e, property-based, and mutation testing with practical patterns
Install
npx skills add cosmicstack-labs/mercury-agent-skills --skill testing-strategiesgit clone --depth 1 https://github.com/cosmicstack-labs/mercury-agent-skills.git /tmp/mercury-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/mercury-agent-skills/categories/development/testing-strategies ~/.claude/skills/testing-strategiesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Testing Strategies A comprehensive approach to testing that gives you confidence your code works correctly — from unit tests to mutation testing. ## Core Principles ### 1. Test Behavior, Not Implementation Your tests should specify what the code does, not how it does it. Tests that pass after a refactor (with the same behavior) are good tests. Tests that break after a refactor (with the same behavior) are brittle tests. ### 2. The Test Pyramid Is a Guideline, Not a Rule Write many fast unit tests, some integration tests, and a few end-to-end tests. But adjust ratios based on your context: a data pipeline needs more integration tests; a UI component needs more visual regression tests. ### 3. Tests Are Code — Treat Them That Way Tests need the same care as production code: clean naming, DRY helpers, proper abstractions. Test code that's hard to maintain leads to tests that get deleted. ### 4. Confidence Is the Goal Coverage numbers are a proxy metric. A codebase with 80% coverage and excellent tests is better than one with 100% coverage and shallow tests. Test the things that scare you. --- ## Testing Maturity Model | Level | Unit Tests | Integration Tests | CI Integration | Quality Gates | |-------|------------|--------------------|----------------|---------------| | **1: None** | No tests | No tests | No CI | None | | **2: Skeleton** | Some critical paths | Happy-path smoke tests | Tests run manually | None |
Details
- Skill name
testing-strategies- Repository
- cosmicstack-labs/mercury-agent-skills
- Path
categories/development/testing-strategies/SKILL.md- License
- MIT
- Repo updated
- 25 August 2026
FAQ
What does the Testing Strategies skill do?
Comprehensive testing strategy covering unit, integration, e2e, property-based, and mutation testing with practical patterns
How do I install the Testing Strategies skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add cosmicstack-labs/mercury-agent-skills --skill testing-strategies. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Testing Strategies popular?
It lives in cosmicstack-labs/mercury-agent-skills, which has 492 GitHub stars and 68 forks.
Related skills
Accessibility
492cosmicstack-labs/mercury-agent-skills
Achieve and maintain WCAG compliance through inclusive design practices, proper ARIA usage, and comprehensive testing methodologies.
Accessibility Testing
492cosmicstack-labs/mercury-agent-skills
WCAG 2.1/2.2 audit, axe, Lighthouse, manual testing, screen reader testing, and remediation
Agent Audit Logging
492cosmicstack-labs/mercury-agent-skills
Implement comprehensive audit logging and reporting for multi-agent systems. Covers event capture, structured logging, traceability, compliance reporting, forensic analysis, and real-time monitoring dashboards for agent actions and decisions.
Fix Issue
220ThinkFlowLab/agentdescent
Fix one AgentDescent issue end to end - claim, fresh clone, a test that fails on main, gates, PR, self-review at the tip, merge by tier, cleanup.
Test Strategy
492cosmicstack-labs/mercury-agent-skills
Test pyramid, risk-based testing, test planning, coverage metrics, and SDLC integration
Desktop A11y Testing Coach
449Community-Access/accessibility-agents
Test desktop apps with NVDA, JAWS, Narrator, VoiceOver and UIA tooling.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.