testing-strategy

Generate test plans, Gherkin examples, and coverage targets for CI validation.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill testing-strategy-camilooscargbaptista
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-strategy
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/testing-strategy
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill testing-strategy-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Testing-strategy helps teams design repeatable, maintainable test suites and QA processes that catch bugs early without slowing delivery. It addresses unclear testing priorities, inconsistent test naming and structure, missing CI validation, and ineffective coverage goals.

Core Features & Use Cases

  • Testing Pyramid Guidance: Advice on how to balance unit, integration, and E2E tests to maximize velocity and signal.
  • TDD & BDD Workflows: Red-Green-Refactor cycle, Gherkin examples, and step definition patterns to align product and engineering.
  • Test Plan & Coverage Targets: Templates for test plans, environment setup, exit criteria, and sensible coverage thresholds by area.
  • Integration & E2E Patterns: Best practices for API, database, migration, and Playwright/Cypress tests and anti-patterns to avoid.
  • Use Case: Create a test plan and CI-ready example tests for a new checkout flow, including unit tests for pricing logic, integration tests for orders API, and an E2E smoke test for purchase.

Quick Start

Ask the testing-strategy skill to produce a CI-ready test plan, example unit tests, and a BDD feature file for the "checkout" feature with recommended coverage targets.

Frequently Asked Questions about testing-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a CI-ready test plan for a new software feature?

A testing strategy balances unit, integration, and E2E tests to maximize velocity and signal. Following the testing pyramid approach prevents slow delivery while catching bugs early without creating ineffective coverage goals.

What is the best way to structure BDD workflows with Gherkin?

BDD workflows align product and engineering using the Red-Green-Refactor cycle, Gherkin examples, and step definition patterns. This approach ensures test suites remain maintainable and clearly communicate feature expectations.

How do I write integration and E2E tests for web and API services?

Apply integration and E2E testing patterns for API, database, and migration tests using Playwright or Cypress. Follow provided best practices and avoid common anti-patterns to ensure tests remain repeatable across CI environments.

How do I set measurable coverage targets for unit testing?

Measurable coverage targets are set by defining sensible coverage thresholds specific to different application areas. This prevents ineffective coverage goals while ensuring maintainability and repeatable CI validation for backend services.

Can I use this testing strategy for both TDD and QA processes?

Yes, this testing strategy supports both TDD and QA processes by delivering test plans, naming and mocking conventions, and integration test patterns. It bridges Red-Green-Refactor development with comprehensive QA validation.