AI Prompts for QA Engineers
50 model-native prompts for Claude, GPT, and Gemini — test design, automation, security, accessibility, CI/CD, and AI agent workflows.
Generate Test Cases from Requirements
Given one requirement, the model returns a structured suite of 8-10 test cases — ID, title, preconditions, steps, expected result, priority, and the design technique that generated each case — covering happy path, negative scenarios, boundary values, equivalence partitions, and edge cases.
Open →Create BDD Scenarios in Gherkin
Reads a user story and returns Cucumber-compatible Gherkin scenarios covering happy path, error scenarios, and at least two edge cases. Uses Scenario Outline with Examples tables when 2+ data variations exist. Forbids UI implementation detail in Then steps.
Open →Exploratory Testing Charter
Returns a Session-Based Test Management charter for a feature area, including a focused mission statement, in-scope areas, applicable testing heuristics by acronym (FEW HICCUPPS, SFDIPOT, RIMGEA), timebox, environment, and a structured notes template.
Open →Generate Test Data Fixtures from Schema
Reads a data schema (JSON Schema, TypeScript type, or table description) and returns four explicit fixture groups — happy path, boundary, invalid, and edge cases. Edge group must include Unicode, RTL, emoji, and injection payloads. Output is a ready-to-import JSON file.
Open →Boundary Value & Equivalence Partition Generator
Reads field constraints (min/max/length/format) and returns boundary and equivalence-partition cases for each — values just inside, on, and just outside the boundary — with technique labels (BVA or EP) per case.
Open →Generate Cypress Page Object Model
Returns a Cypress Page Object class using cy.get() with data-cy preference, action methods that chain via `return this`, plus a commands.js file for cross-page utilities and a sample spec consuming the POM.
Open →Convert Manual Test Cases to Playwright
Reads manual test steps (Action / Expected Result) and produces a Playwright spec with locator suggestions, action method calls (assuming a POM exists), assertions matching expected results, and explicit `// MANUAL:` comments where automation can't replicate human judgment.
Open →Create API Test Suite from OpenAPI Spec
Reads an OpenAPI 3.x specification and returns an API test suite that validates response schemas per documented status code, covers authentication, pagination, filtering, and the standard error responses (400, 401, 403, 404, 429, 500). Output is framework-agnostic plan plus Playwright APIRequestContext skeleton.
Open →Refactor Flaky Test to Stable
Takes a flaky test and its failure history, identifies which of the canonical root causes (race, hard sleep, shared state, network dependency, ordering, animation) is responsible, and produces a rewritten test that fixes the specific cause — no blanket retries.
Open →Generate Test Strategy Document
Returns a full Test Strategy document with 8 mandatory sections — scope, test levels, test types, entry/exit criteria, risk matrix, environment, resources, deprioritized test types — tailored to a product description and stated constraints.
Open →Create Test Plan from PRD
Reads a Product Requirements Document and returns a release-specific Test Plan with scope, milestones, RACI per major activity, deliverables, entry/exit criteria, risk assessment, and a defect management workflow. Uses date placeholders the user fills rather than fabricating.
Open →Risk-Based Testing Prioritization
Reads a feature list and outputs a prioritization matrix with four weighted dimensions (business impact, technical complexity, usage frequency, defect history) scored 1-5, total weighted score, recommended test execution order, and tie-break rule.
Open →Test Pyramid Design for Microservices
Reads a microservices topology (services + integration points) and returns a recommended pyramid distribution with concrete percentages per layer, layer-by-layer justification, explicit contract-test placement at every service boundary, and a strategy for async events.
Open →Test Estimation from User Stories
Reads a backlog of user stories and returns testing effort estimates broken down by activity (test design, execution, automation, reporting) with a confidence level (high/medium/low) and a sanity-check flag when total testing exceeds 50% of dev estimate.
Open →Write a Detailed Bug Report
Takes a free-form issue description (Slack message, email, support ticket) and returns a structured bug report following the AQA Pro Bug Report Template — clear `[Component] Verb-noun` title, environment, separate severity and priority, numbered atomic repro steps, expected vs actual, and suggested investigation areas.
Open →Root Cause Analysis (5 Whys + Fishbone)
Given a defect description, returns a literal 5 Whys chain, a fishbone diagram (text representation) categorizing contributing factors into People / Process / Technology / Environment, and a list of preventive measures with named owners — never generic recommendations.
Open →Bug Triage: Severity and Priority Assigner
Reads a bug description and assigns SEVERITY (impact on system, 1-4) and PRIORITY (urgency to fix, 1-4) on independent scales, each with a written justification, plus a recommended SLA target. Refuses to collapse the two dimensions into one score.
Open →Reproduce a Bug from Logs
Reads application logs, HAR files, or browser console excerpts and reconstructs a step-by-step reproduction recipe with timestamps, the failing request, suspected preconditions, and a confidence flag per inferred step.
Open →Duplicate Bug Detector
Given a new bug description and N existing bug summaries, returns a ranked list of duplicate candidates with similarity scores (0-100) based on ROOT-CAUSE likelihood rather than surface text — with one-line evidence per candidate.
Open →Design a Load Test Strategy
Returns a load test strategy covering 5 scenario types (baseline / load / stress / spike / soak) with thresholds for response time, throughput, and error rate, environment requirements, monitoring checkpoints, and pass/fail criteria — and explicit environment-parity statement.
Open →Generate k6 Test Script from Endpoint
Reads an endpoint description and returns a ready-to-run k6 script with `options.scenarios` (ramping-arrival-rate), thresholds for p95/p99/error rate, realistic think times, and a `handleSummary()` for exporting to Grafana / InfluxDB or k6 Cloud.
Open →Create a JMeter Test Plan
Returns a JMeter test plan as a valid .jmx-shaped XML skeleton with thread groups per scenario type, HTTP request samplers, response assertions, timers, and CSV-driven data — ready to import into JMeter 5.x for refinement and distributed runs.
Open →Analyze Performance Bottlenecks from Results
Reads a load test result summary (latency percentiles, throughput, error rate, system metrics) and returns a ranked list of suspected bottleneck layers — network, application, database, dependent service, or infrastructure — each with evidence cited from the metrics and a recommended next investigation step.
Open →Generate Synthetic Monitoring Scenario
Reads a critical user journey and returns a Playwright-based synthetic monitoring script with business-step checkpoints, failure-screenshot capture, an alerting threshold tied to a stated SLO/SLI, and a recommended run frequency.
Open →Generate Security Test Checklist (OWASP ASVS)
Returns an OWASP ASVS-aligned security testing checklist covering authentication, session management, authorization, input validation, output encoding, cryptography, API security, file upload, and HTTP security headers — each item with a test method (manual / DAST / SAST) and ASVS chapter citation.
Open →Create OWASP Top 10 Test Scenarios
For each OWASP Top 10 (2025) category (A01-A10), returns 3-5 concrete test cases with payloads, recommended tools, expected secure behavior, and remediation guidance tailored to the target application.
Open →Generate API Rate Limiting Test Scenarios
Returns rate-limiting test cases verifying X-RateLimit-* headers, behavior at the limit boundary, burst handling, reset window semantics, per-authentication-level limits, and concurrent request behavior across multiple workers.
Open →Generate Authentication Bypass Test Cases
Returns a structured suite of authentication and authorization bypass test cases — IDOR, JWT algorithm confusion, session fixation, MFA bypass, brute-force resistance, broken object-level authz — with payloads, CWE numbers, and the detection signal that confirms vulnerability vs secure behavior.
Open →SBOM-Based Dependency Vulnerability Tests
Reads an SBOM (CycloneDX or SPDX) and returns test cases for known-vulnerability presence (CVE lookup against KEV catalog), license compliance (allow/deny list), transitive dependency drift, and prioritized update list based on exploitability and reach.
Open →Generate a WCAG 2.2 AA Test Suite
Returns a comprehensive WCAG 2.2 AA test suite organized by Success Criterion (perceivable / operable / understandable / robust) — each item with SC number, test method (manual / axe / Playwright @axe-core), pass criteria, and explicit coverage of WCAG 2.2's new criteria.
Open →Screen Reader Test Scenarios
Reads a component description and returns screen reader test scenarios with expected announcement text per reader (NVDA, JAWS, VoiceOver), recommended browser pairing per reader, navigation pattern, and clear pass/fail criteria.
Open →Keyboard Navigation Test Cases
Returns numbered keyboard navigation test cases covering Tab order, focus visibility, focus trap in modals/menus, Escape key behavior, skip links, focus return after modal close, and roving tabindex for composite widgets — with expected behavior per case.
Open →Color Contrast Audit Generator
Reads a list of foreground/background color pairs and returns contrast ratios, WCAG 1.4.3 (text) and 1.4.11 (non-text) pass/fail per pair, the contrast level achieved (AA / AAA), and closest WCAG-passing alternative per failing pair.
Open →ARIA Patterns Validator
Reads a component's ARIA implementation (role + states + keyboard handling) and validates against the matching WAI-ARIA Authoring Practices Guide pattern — flagging missing required roles, missing required states/properties, incorrect keyboard interactions, and prohibited attribute use.
Open →GitHub Actions QA Pipeline Generator
Returns a complete `.github/workflows/qa.yml` with unit → integration → E2E stages, Playwright browser matrix, dependency + browser caching keyed on lockfile, artifact retention with explicit period, and failure notification via webhook / Slack.
Open →GitLab CI Test Pipeline Configuration
Returns a `.gitlab-ci.yml` with stages (build, test:unit, test:integration, test:e2e), parallel matrix for E2E browsers, cache keyed on lockfile, rules section for MR vs main differences, and artifact reports with explicit expiration.
Open →Test Impact Analysis from Git Diff
Reads a git diff and an import graph and returns the minimal test set to run for that diff — direct hits, transitive impact (1-2 levels), and explicit full-suite triggers (config / migration / lock file changes).
Open →Generate Allure Annotations for Test Files
Reads a test file and annotates each test with Allure metadata (epic, feature, story, severity, link to spec, TMS link) based on file path conventions, commit message JIRA prefixes, and test naming — emits a diff, not a rewrite.
Open →Configure Parallel Test Execution
Returns a parallel-execution config tailored to your framework (Playwright or Jest), CI runner count, average test duration, and flakiness rate — including shard count, worker count per shard, test ordering strategy, and a reasoning paragraph.
Open →Review Test Code for Anti-Patterns
Reads a test file and returns a categorized list of anti-patterns — hard sleeps, shared mutable state, weak assertions (`toBeTruthy` instead of `toEqual`), missing teardown, mixed setup/assertion concerns — each with line numbers, severity, and a suggested fix.
Open →Convert Synchronous Waits to Auto-Waiting
Reads a test using hard waits and returns a rewritten version using Playwright auto-waiting (`expect(locator).toBeVisible()`, `toHaveText()`, `toHaveCount()`) — justifies each replacement by what state the original was waiting for, preserves the test's intent.
Open →Test Code Quality Checklist
Returns a per-test-file quality checklist with 20-30 items grouped by category (naming / structure / assertions / isolation / performance / maintainability) — each marked PASS/FAIL with one-line evidence from the code.
Open →Refactor Test Suite for DRY
Scans a set of test files and identifies duplicated setup, fixture state, and assertion patterns — proposes refactors using Playwright fixtures, factory functions, or shared helper modules with concrete code diffs. Warns against premature abstraction (single-use helpers).
Open →Page Object Model Refactoring Reviewer
Reviews a Page Object Model class and returns specific refactoring suggestions — locator priority (role > label > testid > CSS), action vs assertion separation, action granularity (one method per user intent), and constructor cleanliness — with diff-style proposed changes.
Open →Generate CLAUDE.md for a QA Project
Reads a description of your QA project (framework, language, conventions, CI setup) and returns a ready-to-commit `CLAUDE.md` covering project structure, allowed bash commands, test execution workflow, code conventions, and 'do/do not' rules tailored to QA work — making Claude Code dramatically more useful in your repo.
Open →Generate .cursorrules for a QA Project
Returns a `.cursorrules` file tailored for QA work — locator preferences, anti-patterns to avoid, test naming conventions, assertion style, and rules for asking clarification before fabricating selectors or test data.
Open →Build an AI Bug Triage Workflow
Returns a 5-step AI bug triage workflow (intake → classify → severity → owner assignment → duplicate detection) with the prompt for each step, the structured output schema, and the handoff between steps. Final step emits a structured triage decision.
Open →Generate Test Cases from Figma Design
Reads a Figma design's structured description (frames, interactions, prototype links, states) and returns user-flow test cases plus a Playwright spec scaffold with `data-testid` suggestions matched to design layer names. Flags missing interaction states.
Open →Build an AI PR Review Bot for Test Quality
Returns a prompt + decision framework for an AI PR-review bot tuned for QA — checks for test anti-patterns, missing tests for new branches/conditions, naming convention violations, and assertion quality, with explicit rules for when to comment vs skip and how to phrase comments without false confidence.
Open →Generate Playwright Page Object Model
Give the model a page description plus a list of UI elements and it returns a complete Page Object Model in TypeScript using Playwright's auto-waiting locators (getByRole / getByTestId), typed action and assertion methods, and a page-level fixture.
Open →Frequently asked questions
What are AI prompts for QA?
AI prompts for QA are reusable, structured instructions that get an LLM (Claude, GPT, or Gemini) to produce QA artifacts — test cases, Playwright page objects, bug reports, OWASP scenarios, and CI configs — consistently. A good prompt encodes the format, constraints, and edge cases so output is reliable.
Are these QA prompts free?
Yes. All 50 prompts on AQA Pro are free to copy and use, with Claude (XML-tagged), GPT (Markdown), and Gemini variants. No signup and nothing is uploaded.
Which model should I use for QA prompts?
Use the variant that matches your assistant. Claude variants use XML tags for structure, GPT variants use Markdown sections, and Gemini variants are tuned for its formatting. The underlying task is the same; the structure is model-native.
Can AI prompts replace a QA engineer?
No. Prompts accelerate drafting test cases, scripts, and reports, but a QA engineer reviews coverage, validates edge cases, and owns risk decisions. Treat prompt output as a fast first draft.