Testing Skills

Generate integration tests for REST API endpoints covering auth, validation, success and error responses, and DB side effects. Use when testing endpoints end-to-end or verifying route behavior and data persistence.

Test async UI components (e.g., React) covering loading, success, error, and retry states using proper async queries. Use when testing data-fetching components or avoiding act-related issues.

Write tests against a real test database to verify CRUD operations, queries, constraints, transactions, and migrations. Use when validating DB logic, ORM/repository layers, or data integrity without mocks.

Write E2E tests for full auth flows (register, login, logout, reset, protected routes) with session reuse. Use when testing authentication, session handling, or protected route access end-to-end.

Identify and write E2E tests for the most critical user flows (top 3–5) that impact revenue or retention. Use when defining smoke tests or deciding what to test first.

Write tests for error paths, including exceptions, rejected promises, fallback behavior, and invalid inputs. Use when the user wants to cover failure modes, edge cases, or “unhappy paths.”

Create reusable mock or stub factories that generate configurable, typed fakes for tests. Use when mocks are repetitive, hard to maintain, or need per-test customization.

Test that users cannot access others’ resources, covering IDOR, role violations, and ownership checks. Use when validating authorization, access control, or multi-tenant isolation.

Write tests for background jobs and queue workers covering processing logic, retries, and failure handling. Use when testing workers, job processors, or queue consumers and their behavior.

Create typed fixture and factory systems for test data with sensible defaults and per-test overrides. Use when tests repeat large objects or need reusable data builders.

Fix test isolation by removing shared state, global side effects, and order dependencies. Use when tests are flaky, fail in CI, or pass individually but fail together.

Write tests for third-party integrations using mocks, fixtures, or sandboxes to verify API calls, webhooks, retries, and failure handling without hitting live services.

Generate unit tests covering happy paths, edge cases, boundaries, and error conditions with meaningful assertions. Use when the user asks to write tests, improve coverage, or verify behavior of a function or module.