Senior QA
Generates unit tests, integration tests, and E2E tests for React/Next.js applications.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you write tests for your React checkout component. A good test suite would cover: - Rendering with different props - User interactions like clicking and typing - Form validation - Success and error states - Edge cases like empty cart You'd typically use Jest with React Testing Library for component tests. For end-to-end flows, Playwright or Cypress works well. Mocking the API calls is important so tests are reliable. Share the component and I can suggest specific test cases.
TEST SUITE — React checkout. Generated by scanning the component, not guessing at it. Three layers, because checkout needs all three. UNIT (Jest + React Testing Library) — from the component's actual props ✓ renders line items from cart prop ✓ disables "Pay" when cart is empty ✓ shows validation error on invalid card, no submit ✓ calls onSubmit with the right payload on valid input API calls mocked with MSW — so tests don't hit a real endpoint and aren't flaky. E2E (Playwright) — scaffolded from your Next.js routes ✓ /cart → /checkout → /confirmation happy path ✓ declined-card path shows the error state, stays on /checkout These are the ones that catch the real checkout bugs — the button that works in a unit test but is off-screen in a real browser. COVERAGE-DRIVEN GAP FILL Reads your Istanbul/LCOV report and surfaces what's UNtested — so you're not writing your 40th happy-path test while the error branch has zero coverage. The gaps are where the bugs live. FIXTURES A cart fixture (empty, one item, many items) reused across all tests, so a data-shape change is one edit, not forty. THE ORDER THAT MATTERS Unit for logic, E2E for the money path, coverage report to find the holes. On checkout, the declined-card E2E is the test I'd write first — it's the one that costs revenue when it breaks. Point me at the component and your route folder and I'll generate the stubs.
About this skill
name: senior-qa description: Use when Generates unit tests, integration tests, and E2E tests for React/Next.js applications.
Senior Qa
Generates unit tests, integration tests, and E2E tests for React/Next.js applications. Scans components to create Jest + React Testing Library test stubs, analyzes Istanbul/LCOV coverage reports to surface gaps, scaffolds Playwright test files from Next.js routes, mocks API calls with MSW, creates test fixtures, and configures test runners. Use when the user asks to "generate tests", "write unit tests", "analyze test coverage", "scaffold E2E tests", "set up Playwright", "configure Jest", "implement testing patterns", or "improve test quality".
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the senior-qa skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Senior Qa; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: senior-qa
description: Use this skill when unit, integration, or end-to-end tests need generating for a React or Next.js application, or when test coverage needs analyzing.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Senior Qa
Generates unit, integration, and end-to-end tests for React and Next.js applications: Jest and React Testing Library stubs, coverage gap analysis, and Playwright scaffolds from actual routes.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.