testing

Generate GitHub Actions workflow for test suites, avoiding duplication with existing CI pipelines

Generate test suites automatically by detecting project stack and analyzing source code

---

Run comprehensive test suite with auto-detection across unit, smoke, API contract, and E2E testing

Generate comprehensive frontend test suites for React/Next.js applications including component, visual regression, accessibility, and performance tests based on implementation analysis

Detect test frameworks, coverage tools, CI config. Populates .claude/project.json testing key.

Generates comprehensive test suites from implementation analysis

Execute tests across all detected frameworks with result aggregation and CI-awareness

Reads package.json testing config and generates complete test suites (Jest, React Testing Library, Playwright) based on project structure and testing parameters

OpenAPI to Portman to Newman pipeline with auth injection for API contract testing. Use when building API tests from OpenAPI specs, injecting authentication into test collections, running contract tests, or when user mentions OpenAPI, Portman, API contract, Swagger, API testing pipeline, auth injection.

Comprehensive frontend testing patterns including component tests (Jest/Vitest + RTL), visual regression (Playwright), accessibility (axe-core), and performance (Lighthouse) testing for React/Next.js applications. Use when building frontend tests, testing React components, implementing visual regression, running accessibility tests, performance testing, or when user mentions component testing, visual regression, a11y testing, React Testing Library, Jest, Vitest, Lighthouse, or frontend testing.

Run and analyze Newman (Postman CLI) tests. Use when running API tests, validating Postman collections, testing HTTP endpoints, or when user mentions Newman, Postman tests, API validation.

Playwright end-to-end testing patterns including page object models, test scenarios, visual regression, and CI/CD integration. Use when building E2E tests, testing web applications, automating browser interactions, implementing page objects, running Playwright tests, debugging E2E failures, or when user mentions Playwright, E2E, browser automation, page object model, POM, visual regression, or end-to-end testing.

Health endpoint and critical path smoke testing patterns. Use when running quick validation tests, checking health endpoints, verifying critical paths respond correctly, or when user mentions smoke testing, health checks, quick validation, sanity checks.

Detection scripts and patterns for identifying test frameworks across all supported languages. Use when detecting test infrastructure, analyzing project testing setup, identifying coverage tools, or when user mentions test detection, framework identification, testing setup analysis.