Agent skill · software engineering · borghei
senior-qa
Testing for React/Next.js with Jest, React Testing Library, and Playwright. Use when generating tests, writing unit tests, analyzing coverage, scaffolding E2E tests, configuring Jest, or improving test quality.
Why this skill is useful
Adds 3 executable scripts for generating Jest test stubs, analyzing coverage, and scaffolding Playwright tests that extend the AI's capabilities in QA automation.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Senior QA Engineer Test automation, coverage analysis, and quality assurance patterns for React and Next.js applications. Generates Jest + React Testing Library unit test stubs, analyzes Istanbul/LCOV coverage for gaps, and scaffolds Playwright E2E suites for App Router and Pages Router projects. Core Capabilities Unit test generation — scan React/TypeScript components and emit Jest + RTL stubs (render, interaction, state, optional jest-axe a11y). Coverage analysis — parse Istanbul/LCOV reports, identify gaps by severity, flag critical business-logic paths, and emit text/HTML/JSON recommendations. E2E scaffolding — detect Next.js routes (dynamic segments, route groups, auth pages) and generate Playwright specs, Page Object Models, fixtures, and config. Test strategy — the testing pyramid, coverage targets by code type, and test organization patterns. Automation patterns — Page Object Model, data factories, MSW mocking, fixtures, and custom render utilities. Quality practices — testable code design, AAA structure, test isolation, flaky-test elimination, and quality metrics. When to Use Setting up unit tests for new or existing React components. Improving test coverage or preparing for release. Setting up Playwright E2E tests for a Next.js project. Configuring Jest thresholds or improving overall test quality. Clarify First Before generating tests, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Test layer — unit (Jest+RTL) vs E2E (Playwright) (selects testsuitegenerator vs e2etestscaffolder) [ ] Source path — the components or Next.js routes to generate tests from (the scaffolder's input) [ ] Coverage focus — happy path only vs interaction/state/a11y (jest-axe) (sets which test stubs are emitted) Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/senior-qa