qa-engineer

Writes and executes unit, integration, contract, e2e, and performance test suites for services and frontends.

176|49|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/nagisanzenin/production-grade --skill qa-engineer-nagisanzenin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-engineer
Source: https://github.com/nagisanzenin/production-grade/tree/main/skills/qa-engineer
Command: npx skills add https://github.com/nagisanzenin/production-grade --skill qa-engineer-nagisanzenin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Verifying that generated or existing code actually works requires a complete, executable test strategy — most projects end up with scattered happy-path tests that miss integration failures, contract drift, and performance regressions. ## Core Features & Use Cases - Full test pyramid generation: Produces unit, integration (testcontainers/docker-compose), contract (Pact/OpenAPI schema), E2E (Playwright/Cypress), and performance (k6) tests under a dedicated tests/ tree, traced to BRD acceptance criteria via a traceability matrix. - Oracle ownership and TDD pairing: Writes failing acceptance scaffolds first, then guards the tests/ tree against weakening by other agents, flagging skipped or loosened assertions as critical findings. - Execution with real numbers: Runs every suite it writes and reports tests_run/tests_passing/tests_failing, plus CI workflow configuration with coverage thresholds and flaky-test handling. - Use Case: After backend and frontend code is generated, invoke this skill to produce a test plan, all test suites, CI test workflow, and an execution report proving which acceptance criteria pass. ## Quick Start Ask the agent to write and run a complete test suite covering unit, integration, and e2e flows for the services in this project.

Frequently Asked Questions about qa-engineer

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

FAQPage Schema
How do I generate a complete test suite for my backend services?▼

This skill reads your services, API contracts, and BRD acceptance criteria, then produces a traceability matrix and writes unit, integration, contract, e2e, and performance tests under a tests/ directory. It runs the suites and reports exact passing and failing counts.

What testing frameworks does it use for e2e and performance tests?▼

E2E tests use Playwright or Cypress with Page Object Model patterns and data-testid selectors. Performance tests use k6 scripts for load, stress, and spike scenarios with baseline JSON files and p95/p99 latency thresholds.

Can it write integration tests against a real database?▼

Yes. Integration tests use docker-compose or testcontainers with pinned image versions for PostgreSQL, Redis, Kafka, and similar dependencies. Tests run against real instances with cleanup via transactions or table truncation, never mocking the dependency under test.

Does it work when the project has no frontend directory?▼

Yes. At startup it checks for the frontend directory and degrades gracefully, skipping UI e2e, visual regression, and frontend contract tests while continuing all backend test phases normally.

Why do generated tests fail when run in CI but pass locally?▼

Common causes are hardcoded ports, connection strings, or shared mutable state between tests. This skill avoids those by using environment variables, per-test data factories, unique identifiers for parallelization, and explicit wait conditions instead of sleep calls.