skills.rest
andrew-tucker-razorvision
andrew-tucker-razorvisionCOMMUNITY
Explore all skills by this author →
GitHub

testing-strategy

Plan unit, integration, E2E, and smoke tests for EFT-Tracker.

Updated Aug 23, 2026
Search Tags:#vitest#testing#integration testing#unit testing#e2e#Playwright#MSW
One-click install
npx skills add https://github.com/andrew-tucker-razorvision/EFT-Tracker --skill testing-strategy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-strategy
Source: https://github.com/andrew-tucker-razorvision/EFT-Tracker/tree/main/.claude/skills/testing-strategy
Command: npx skills add https://github.com/andrew-tucker-razorvision/EFT-Tracker --skill testing-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a clear test pyramid, decision trees, MSW patterns, and Playwright best practices to guide where and how to test EFT-Tracker.

Core Features & Use Cases

  • Test Pyramid: Unit/Integration/E2E distribution
  • MSW patterns: API mocking; Playwright guidelines
  • Contracts & checks: Pre-test checklists

Quick Start

Run unit tests for pure utilities first; add MSW mocks for API routes.

Frequently Asked Questions about testing-strategy

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

FAQPage Schema
How do I structure a testing strategy across unit, integration, and E2E tests?▼

A testing strategy balances test types by distribution: unit tests (49%) for isolated logic, integration tests (49%) for component and API interactions, and E2E tests (2%) for critical user journeys. This pyramid approach maximizes coverage efficiency while keeping test maintenance low.

What's the best way to mock APIs in integration tests?▼

MSW (Mock Service Worker) intercepts API requests at the network layer, letting you define mock handlers for routes and responses. This approach works across unit and integration tests without modifying application code.

How do I decide whether to write a unit, integration, or E2E test?▼

Use a decision tree: unit tests for pure functions and utilities, integration tests for components with API calls or state, and E2E tests only for critical user workflows. This prevents over-testing and keeps your suite fast.

Can I use Vitest and React Testing Library together for frontend testing?▼

Yes. Vitest runs the tests, React Testing Library queries components by user-visible behavior, and MSW mocks API responses. This combination covers unit and integration scopes for frontend features.

What Playwright best practices should I follow for E2E tests?▼

Playwright best practices include targeting user-facing selectors, avoiding flaky waits, and testing only critical paths. Combined with contract testing via TS+Zod API definitions, E2E tests stay maintainable and focused.

Do I need contract testing before writing integration tests?▼

Contract testing with TS+Zod validates API request and response shapes upfront, preventing mismatches in integration tests. This pre-test check catches schema issues early and reduces debugging.

Related Skills

Explore More Software Engineering Skills→
lsst-sqrelsst-sqre
2

testing-infrastructure

Configure Vitest, React Testing Library, and MSW mocks for monorepo CI testing.

Official
Intermediate
cbbkrd-techcbbkrd-tech

ln-782-test-runner

Executes detected test suites and parses pass/fail counts with coverage reports.

Community
Advanced
mindcockpit-aimindcockpit-ai
11

react-testing

Integrate Vitest, React Testing Library, MSW v2, and Playwright for React UI testing.

Official
Advanced
interserverinterserver
1

mocha-skill

Generate Jest-free unit tests with Mocha, Chai, and Sinon.

Official
Intermediate