Skip to content
Skills Library
Programming · Planning

dev-test-strategy

/dev-test-strategy

Use to design or validate test plans, unit/integration/e2e coverage, automation, CI checks, fixtures, and regression scope.

Licence
GPL-3.0
Last repository change
17.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 17.09.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Use to design or validate test plans, unit/integration/e2e coverage, automation, CI checks, fixtures, and regression scope.

Original author description

Use to design or validate test plans, unit/integration/e2e coverage, automation, CI checks, fixtures, and regression scope.

How it works

  1. Steps
  2. Output
  3. Do not
Original SKILL.md headings · 56 lines, 226 words
SKILL.md preview
---
name: dev-test-strategy
description: Use to design or validate test plans, unit/integration/e2e coverage, automation, CI checks, fixtures, and regression scope.
metadata:
  version: "0.3"
  updated: "2026-06-12"
---

# Test strategy workflow

Use this workflow when a software task needs test planning, test implementation, or validation triage.

## Steps

1. Map existing tests.
   - Test framework
   - Test directories
   - Fixtures and factories
   - CI commands
   - Coverage expectations
   - Known flaky tests

2. Identify changed behavior.
   - Public API or CLI behavior
   - UI behavior
   - Data model or migration
   - Auth/permissions
   - Error paths
   - Performance-sensitive path

3. Choose test levels.
   - Unit tests for isolated logic
   - Integration tests for components/services/databases
   - Contract/API tests for boundary behavior
   - UI/e2e tests for user workflows
   - Regression tests for bugs

4. Keep validation efficient.
   - Run the smallest relevant check first.
   - Broaden only when the change or failure requires it.
   - Capture exact command, status, and important output.

5. Handle failures honestly.
   - Separate failure caused by current change from pre-existing failure.
   - State flaky or inconclusive results.
   - Do not weaken tests to pass.

## Output

Return:

1. Behavior under test
2. Existing coverage
3. Added or recommended tests
4. Commands run
5. Remaining test gaps

## Do not

- Do not claim coverage without reading or running the relevant tests.
- Do not add brittle UI or timing tests when lower-level tests cover the behavior better.
- Do not skip changed behavior just because the current test suite is thin.

Versions

The database has no other skills named dev-test-strategy.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 2105466d3875 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100post-dev-test
    Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
  • 90test-strategy
    Design a pragmatic test strategy: pyramid, unit/integration/e2e/contract split, fixtures, flakiness, coverage and mutation testing, CI speed. Use when planning tests, fixing weak or flaky suites, or deciding what to test.
  • 100testing-engineering
    Use when designing test strategies, authoring unit/integration/E2E tests, analyzing test failures, setting up test fixtures, measuring meaningful coverage, or producing verification reports.
  • 100testing-strategy
    Testing approach covering unit/integration/e2e split, what to test, AAA test structure, mocking strategies, and coverage targets. Use when writing tests, planning test coverage, or reviewing test quality.
  • 100test-automation-strategy
    Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency.
  • 95testing-quality-engineering
    Use this capability for test plans, unit/integration/e2e tests, contract tests, property tests, snapshot strategy, mocks, test data, coverage, flaky tests, regression suites, quality gates, AI evals, and release verification. Trigger on test, QA, coverage, flaky, regression,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.