Menu
Designs unit, integration and end-to-end testing strategies and implements tests for code changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guides the creation and review of Architectural Decision Records (ADRs). Use this skill when a significant architectural change is proposed, a new technology is introduced, or a trade-off needs to be documented.
Intelligently routes requests to the correct context instructions and documentation files. Use this skill to determine which AGENT.md, guide, or technical instruction file is most relevant for a user's request.
Scaffold API mocking infrastructure using Mountebank and Testcontainers for reliable integration testing.
Manage full-stack observability using Logfire (logging/tracing) and OpenObserve (storage/visualization).
Interface for managing the Temporal Database and AI system (ReDB + GGUF embeddings).
Spec-Driven Development workflow using VibesPro conventions
| name | testing-strategy |
| description | Designs unit, integration and end-to-end testing strategies and implements tests for code changes. |
| metadata | {"id":"ce.skill.testing-strategy","tags":["testing","validation","performance"],"inputs":{"files":["ARCHITECTURE.md","CONTRIBUTING.md"],"concepts":["test-pyramid"],"tools":["toolset:write"]},"outputs":{"artifacts":["ce.task.validate"],"files":[],"actions":["apply-changes"]},"dependsOn":{"artifacts":["ce.task.validate"],"files":[".vscode/tasks.json"]},"related":{"artifacts":["ce.prompt.write-tests"],"files":[]}} |
This skill ensures that new features are accompanied by robust tests across the testing pyramid.
Review context. Load ARCHITECTURE.md and CONTRIBUTING.md to understand the system
architecture, critical paths and existing testing conventions.
Plan test coverage. Determine which layers of the testing pyramid apply:
Identify key scenarios. For each requirement or plan step, outline the positive, negative and edge case scenarios that must be tested. Consider performance and security aspects where applicable.
Select frameworks and tools. Choose appropriate testing frameworks (e.g. pytest for Python, Jest for JS/TS) and any mocking or fixture libraries. Ensure tests can run in isolation and in CI.
Write and organise tests. Implement the tests following language-specific best practices. Place them in clearly named files and directories. Use descriptive test names and assertions.
Run and iterate. Execute the tests locally. Fix any failing tests or code issues. Ensure the entire suite passes quickly. Address flakiness or excessive coupling.
Validate and summarise. Run the validation task to ensure no structural issues were introduced. Summarise the new tests and their coverage. Highlight any remaining gaps for future work.
Embedding testing as a first-class activity guarantees reliability and facilitates confident refactoring.
