testing-strategy

What This Skill Does

The testing-strategy skill acts as a senior QA architect and DevOps consultant within your workflow. It shifts focus from arbitrary metrics like 'code coverage percentages' to a risk-aware testing framework. It guides you through a six-stage methodology to design, implement, and maintain a robust testing ecosystem. The skill analyzes your current development lifecycle, helping you define clear boundaries for unit, integration, and end-to-end tests, while establishing CI gates that balance speed with reliability. It specifically targets common pain points like brittle, flaky CI pipelines, high maintenance costs, and ambiguous ownership between developers and QA.

Installation

To add this skill to your workspace, execute the following command in your terminal: clawhub install openclaw/skills/skills/clawkk/testing-strategy

Use Cases

• Major Architectural Refactors: When moving from a monolith to microservices, use this skill to define contract testing and integration strategies that prevent cascading failures.
• CI/CD Stabilization: If your CI pipeline is perpetually broken or 'flaky,' this skill provides a triage process for identifying, quarantining, and resolving non-deterministic tests.
• Resource Allocation Strategy: Use the framework to decide whether your project needs dedicated QA headcount or if shifting-left and developer-authored automation is the more efficient path.
• New Product Inception: When starting a new service, use the 'risk register' phase to identify which business logic paths are mission-critical, ensuring they are protected by high-confidence tests before code is even written.

Example Prompts

1. 'Our E2E tests are taking 45 minutes to run and fail randomly. Can you help me apply the testing-strategy framework to identify how we can move some of these to faster integration or unit layers?'
2. 'We are starting a new payment service. Guide me through a risk mapping session to determine our top 5 failure categories and the corresponding testing intent for each.'
3. 'Help me draft a test policy for our team that clearly defines what should be a unit test versus an integration test, keeping our developer workflow speed in mind.'

Tips & Limitations

• Proactive Implementation: This skill works best when consulted before writing significant amounts of tests, rather than as a post-mortem tool.
• Context is Key: Provide the agent with details about your current technology stack (e.g., Docker, Kubernetes, specific languages) to get the most accurate advice on tools like Testcontainers or mocking libraries.
• Team Buy-in: The strategy is a cultural change as much as a technical one. Use the 'exit conditions' provided in the framework to ensure your team is aligned on the definition of 'done' for each test layer before moving forward.