Przejdź do treści
Biblioteka skilli
Programowanie · Testowanie

testing-strategy

/testing-strategy

Projektuje architekturę testów: piramidę, testy API i komponentów, MSW, Playwright i integrację z CI.

Repozytorium
pokayokay ↗
Licencja
MIT
Ostatnia zmiana repozytorium
28.09.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
24
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 28.09.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Projektuje architekturę testów: piramidę, testy API i komponentów, MSW, Playwright i integrację z CI.

Oryginalny opis (EN)

Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.

Jak działa

  1. Test Pyramid
  2. Key Principles
  3. When NOT to Use
  4. Quick Start Checklist
  5. What NOT to Test
  6. References
  7. Runtime Notes
Sekcje z nagłówków SKILL.md, w oryginale · 78 linii, 582 słów
Podgląd SKILL.md
---
name: testing-strategy
description: Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.
---

# Testing Strategy

Comprehensive testing guidance for test architecture, coverage strategy, and test design.

## Test Pyramid

| Level | Speed | Cost | Confidence | Share |
|-------|-------|------|------------|-------|
| **Unit** | ~1ms | Low | Narrow | 65-80% |
| **Integration** | ~100ms | Medium | Medium | 15-25% |
| **Contract** | ~10ms | Low | API shape | Part of unit |
| **E2E** | ~1s+ | High | Broad | 5-10% |

## Key Principles

- Test behavior, not implementation — test what code does, not how
- For behavior changes, write the failing test first and verify it fails for the expected reason
- Follow the testing pyramid — more unit tests, fewer E2E
- Use meaningful coverage metrics — branch coverage over line coverage
- Prevent flaky tests — no arbitrary waits, no test interdependence

## When NOT to Use

- For TDD discipline during implementation — see work-session anti-rationalization reference
- For security testing — see security-audit skill

## Quick Start Checklist

1. Choose test framework (Vitest recommended for new projects)
2. Design test folder structure mirroring source
3. Write unit tests for pure logic and utilities
4. Add integration tests for API endpoints and data flows
5. Add contract tests against OpenAPI spec (if applicable)
6. Add E2E tests for critical user journeys only
7. Set up CI to run tests on every PR
8. Before completion claims, run `verification-before-completion` and cite the fresh command result

## What NOT to Test

- Framework internals (React rendering, Express routing)
- Third-party library behavior
- Trivial getters/setters with no logic
- Implementation details (private methods, internal state)

## References

| Reference | Description |
|-----------|-------------|
| [test-architecture-structure.md](references/test-architecture-structure.md) | Project structures, shared utilities, test configuration |
| [test-architecture-isolation.md](references/test-architecture-isolation.md) | Playwright config, database isolation, performance optimization |
| [test-design-techniques.md](references/test-design-techniques.md) | Equivalence partitioning, boundary values, decision tables, state transitions |
| [test-design-error-and-advanced.md](references/test-design-error-and-advanced.md) | Error handling tests, property-based testing, parameterization, regression |
| [frontend-react-testing.md](references/frontend-react-testing.md) | React Testing Library, queries, user events, hooks, forms |
| [frontend-vue-a11y-visual.md](references/frontend-vue-a11y-visual.md) | Vue Test Utils, accessibility, visual/Storybook testing, anti-patterns |
| [e2e-playwright.md](references/e2e-playwright.md) | Playwright POM, fixtures, auth state, API mocking, visual comparison |
| [e2e-cypress-and-stability.md](references/e2e-cypress-and-stability.md) | Cypress patterns, flaky test prevention, test data, debugging |
| [mocking-fundamentals.md](references/mocking-fundamentals.md) | Mock decision tree, stubs/mocks/spies/fakes, MSW setup and usage |
| [mocking-modules-and-patterns.md](references/mocking-modules-and-patterns.md) | Module mocking, time mocking, anti-patterns, dependency injection |
| [coverage-guide.md](references/coverage-guide.md) | Coverage metrics, meaningful thresholds, CI integration |
| [api-test-frameworks-setup.md](references/api-test-frameworks-setup.md) | Vitest and Jest setup, configuration, running tests |
| [api-test-supertest-and-helpers.md](references/api-test-supertest-and-helpers.md) | Supertest usage, request helpers, custom matchers, snapshots, debugging |
| [api-integration-patterns.md](references/api-integration-patterns.md) | CRUD endpoint tests, relationship tests |
| [api-auth-patterns.md](references/api-auth-patterns.md) | Login/logout, protected routes, authorization, auth helpers |
| [api-e2e-and-edge-cases.md](references/api-e2e-and-edge-cases.md) | Multi-step workflow tests, error responses, edge cases |
| [api-test-data-factories.md](references/api-test-data-factories.md) | Factory patterns, builders, fixtures |
| [api-test-data-database.md](references/api-test-data-database.md) | Database helpers, cleanup strategies, data generation |
| [api-contract-openapi.md](references/api-contract-openapi.md) | OpenAPI/AJV schema validation, contract tests |
| [api-contract-zod-advanced.md](references/api-contract-zod-advanced.md) | Zod validation, response shape testing, breaking change detection |
| [api-test-ci-pipelines.md](references/api-test-ci-pipelines.md) | CI pipeline strategy, GitHub Actions, parallel execution |
| [api-test-ci-environments.md](references/api-test-ci-environments.md) | Environment config, test reporting, database services, E2E environments |
| [anti-rationalization.md](references/anti-rationalization.md) | Iron Law, common rationalizations, red flag STOP list for TDD discipline |

## Runtime Notes

- **Claude Code**: dispatch yokay-test-runner via the Task tool with `subagent_type: "pokayokay:yokay-test-runner"`.
- **Codex**: there is no subagent dispatch. Execute the agent's role inline — read the corresponding `agents/yokay-<name>.md` and follow its Behavioral Defaults, Critical Rules, and Output Contract directly in the current session.
Pliki w paczce (24)
  • SKILL.md 5 KB
  • references/anti-rationalization.md 4 KB
  • references/api-auth-patterns.md 8 KB
  • references/api-contract-openapi.md 9 KB
  • references/api-contract-zod-advanced.md 11 KB
  • references/api-e2e-and-edge-cases.md 10 KB
  • references/api-integration-patterns.md 8 KB
  • references/api-test-ci-environments.md 9 KB
  • references/api-test-ci-pipelines.md 8 KB
  • references/api-test-data-database.md 10 KB
  • references/api-test-data-factories.md 7 KB
  • references/api-test-frameworks-setup.md 5 KB
  • references/api-test-supertest-and-helpers.md 10 KB
  • references/coverage-guide.md 10 KB
  • references/e2e-cypress-and-stability.md 10 KB
  • references/e2e-playwright.md 5 KB
  • references/frontend-react-testing.md 8 KB
  • references/frontend-vue-a11y-visual.md 7 KB
  • references/mocking-fundamentals.md 7 KB
  • references/mocking-modules-and-patterns.md 5 KB
  • references/test-architecture-isolation.md 5 KB
  • references/test-architecture-structure.md 8 KB
  • references/test-design-error-and-advanced.md 8 KB
  • references/test-design-techniques.md 8 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · srstomp/pokayokay90MIT
komluk/scaffolding100MIT
oborchers/fractional-cto100MIT
anastasiyaw/codex-claude-code-config100MIT
andreibesleaga/gabbe100CC-BY-4.0
organizzolini/codebase100MIT
shinpr/agentic-code100MIT
sagargupta16/claude-code-recipes100MIT
officialdb/TES-SKILLS100Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki a4784610f1ab (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100frontend-testing-strategy
    Planuje niezawodny zestaw testów frontendu: poziomy testów, piramidę, testy zachowania, mockowanie API, dostępność i testy wizualne.
  • 90frontend-testing
    Planuje i konfiguruje testy frontendu w TypeScript: Vitest z Testing Library, MSW do mocków API, Playwright do testów E2E oraz progi pokrycia w CI.
  • 95qa-strategy
    Projektuje strategię testów: piramidę testów, architekturę E2E, wydajność i proces triage błędów.
  • 100nextjs-testing
    Pisze testy jednostkowe Jest lub Vitest z React Testing Library oraz testy E2E Playwright dla projektów Next.js, w tym mockowanie API przez MSW.
  • 100react-testing
    Pomaga pisać i naprawiać testy komponentów, hooków i stron React w Testing Library, z MSW i axe.
  • 100eng-testing
    Prowadzi przy pisaniu testów, projektowaniu strategii testów i przeglądzie pokrycia: piramidę testów, nazewnictwo, mockowanie i politykę testów niestabilnych.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.