- Home
- Skills
- Ariegoldkin
- Ai Agent Hub
- Testing Strategy Builder
testing-strategy-builder_skill
- TypeScript
8
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill ariegoldkin/ai-agent-hub --skill testing-strategy-builder- SKILL.md14.0 KB
Overview
This skill helps you create comprehensive testing strategies that improve reliability, maintainability, and release confidence. It provides templates, coverage targets, test case structures, and guidance for unit, integration, E2E, and performance testing. Use it to establish quality gates, pick tools, and design CI-driven test workflows. The goal is practical, risk-based test planning across the development lifecycle.
How this skill works
I guide you through selecting appropriate tools and defining coverage goals based on project risk and architecture. The skill supplies test-plan and test-case templates, checklists, and example patterns (AAA, Given-When-Then, Testing Trophy). I recommend a CI integration strategy with quality gates, and provide advice for test data management, isolation, and performance scenarios. Recommendations adapt to frameworks like React, Vue, FastAPI, and Django.
When to use it
- Planning testing strategy for a new project or major feature
- Improving or auditing test coverage in an existing codebase
- Defining CI/CD quality gates and automated test pipelines
- Designing test automation architecture and selecting tools
- Preparing performance and load-testing plans for production endpoints
Best practices
- Prioritize risk-based coverage: 95-100% for critical paths, ~80% overall as a minimum
- Favor fast, deterministic unit tests and more integration tests for component interactions
- Keep tests isolated: fresh test DBs, clean up resources, avoid order dependencies
- Use mocking for slow/third-party services and real dependencies for core business logic
- Run static analysis (lint, typecheck) on every commit and full suites on PRs
Example use cases
- Define coverage targets and quality gates for a payment-enabled web app
- Create CI pipeline stages: lint, typecheck, unit/integration, coverage upload, E2E, performance
- Draft test-plan and test-case documents for a new microservice with DB interactions
- Design k6 load tests for critical API endpoints and automate performance checks on main
- Convert flaky E2E tests into reliable integration + focused E2E journeys using Testing Trophy
FAQ
Use 80% overall as a baseline, require 95-100% for critical paths (payments, auth), and enforce 100% for new feature code where practical.
How many E2E tests are enough?
Focus on 5-10 critical user journeys that validate end-to-end behavior; keep most checks at integration and unit levels for speed and reliability.