agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/test-strategy/SKILL.md

test-strategy

Skill2 starsChanged 6 months agoMITView on GitHub

Test strategy design, test writing guide, and coverage targets. Use when writing tests, designing test plans, setting up test infrastructure, or evaluating test quality. Provides patterns for unit, integration, E2E, and API testing.

41 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use database-testing, exploratory-testing and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • petrkindlmannSkill

    database-testing

    Validate database integrity, test migrations forward and backward, verify schema constraints, manage seed data, detect migration drift, and identify query performance issues. Covers PostgreSQL, MySQL, MongoDB with Prisma, TypeORM, Drizzle, and SQLAlchemy, plus Testcontainers test databases. Use when: "database test," "migration test," "migration rollback," "rollback test," "data integrity," "SQL test," "schema validation," "seed data," "query performance," "Testcontainers." Not for: synthetic data generation/masking at scale — use test-data-management; Docker/IaC test-environment provisioning — use test-environments; SQL injection — use security-testing. Related: test-data-management, test-environments, security-testing, ci-cd-integration.

    Also in 3 projects that use this

  • testified-ossSkill

    exploratory-testing

    Guide exploratory testing sessions including charter creation, session-based testing, heuristics application, and finding documentation. Use when planning exploratory testing, conducting test sessions, or documenting discoveries.

    Also in 4 projects that use this

  • YepAPISkill

    data-pipelines

    ETL patterns, cron scheduling, queue-based processing, and batch jobs with Inngest/BullMQ.

    Also in 3 projects that use this

  • ffsshhttiikkSkill

    unit-testing

    Unit testing best practices and patterns

    Also in 4 projects that use this

  • AnthropicSkill

    incident-response

    Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

    Also in 7 projects that use this

  • OpenAISkill

    observability

    Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the test pyramid for cost-effective coverage:

    line 31

“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Testing Procedures

Systematic testing skill covering strategy, patterns, and quality gates. Produces consistent, maintainable test suites across tech stacks.

When to Use

  • Writing new tests for features or bug fixes
  • Designing test strategy for a new project or module
  • Evaluating existing test coverage and quality
  • Setting up test infrastructure (fixtures, factories, mocks)
  • Creating or updating TESTING.md documentation

When NOT to Use

  • Running tests (use run-tests skill workflow instead)
  • Reviewing test code quality (use code-review skill)
  • Validating CI pipeline configuration (use devops-engineer role)

Test Pyramid

Follow the test pyramid for cost-effective coverage:

        /  E2E  \           Few — critical user journeys only
       /----------\
      / Integration \       Moderate — API, DB, service boundaries
     /----------------\
    /    Unit Tests     \   Many — fast, isolated, comprehensive
   /--------------------\
LayerWhat to TestSpeedCount
UnitPure logic, transformations, validators, utils< 50msMany
IntegrationDB queries, API endpoints, service interactions< 5sModerate
E2ECritical user journeys, happy paths, key flows< 30sFew

Test Design Principles

  1. Test behavior, not implementation — assert outcomes, not internal calls
  2. One assertion per concept — each test verifies one logical thing
  3. Arrange-Act-Assert — clear structure in every test
  4. Deterministic — no flaky tests. Mock time, randomness, external services
  5. Independent — tests must not depend on execution order
  6. Descriptive names — test name describes the scenario: should_return_404_when_user_not_found
  7. Fast feedback — unit tests run in seconds, not minutes

Coverage Targets

MetricTargetHard Minimum
Line coverage≥ 80%≥ 60%
Branch coverage≥ 75%≥ 50%
Critical path coverage100%100%
New code coverage≥ 90%≥ 80%

Critical paths = authentication, authorization, payment, data mutations, error handling.

Key Context File

Projects should have a TESTING.md at the root (and per-service in monorepos) documenting test infrastructure, commands, credentials, and organization. Created by project-init skill using qa-engineer role. Always read TESTING.md before writing or running tests.

Integration

  • Follows rules: qa-engineer role (test strategy, automation, local test infra), software-engineer role (code quality)
  • Used by workflows: test-local skill (full local QA cycle), run-tests skill (lightweight execution), project-init skill (TESTING.md generation), feature-dev skill, bugfix skill, pre-commit skill
  • Companion resources: test-writing-guide.md
  • Template: templates/testing.template.md (root + per-service TESTING.md templates)
  • Project context: TESTING.md (root + per-service)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.