Use case
Use this when you have a new feature, ticket, or product requirement and want a structured QA plan.
Best for
QA engineers, product teams, and developers starting new feature work.
QA prompts library
Use these prompts to turn product requirements, bug reports, user flows, pull requests, and application URLs into better QA work. AlwaysQA helps your AI agent think like a QA engineer.
25
Ready prompts
10
Workflow areas
Local-first
Agent QA workflows
Use the prompts below inside your coding agent, QA workflow, or AlwaysQA MCP-connected environment.
Requirements to QA coverage
Test planning
Turn product requirements, user stories, test data needs, and implementation plans into structured QA coverage.
Use case
Use this to transform a Jira, Linear, or GitHub issue into concrete test cases.
Best for
QA engineers, product teams, and developers starting new feature work.
Use case
Use this when QA needs realistic data sets for positive, negative, boundary, and role-based testing.
Best for
QA engineers, product teams, and developers starting new feature work.
Use case
Use this before implementation starts so developers can spot likely bugs early.
Best for
QA engineers, product teams, and developers starting new feature work.
Use case
Use this when the team has too many manual tests and needs a rational automation order.
Best for
QA engineers, product teams, and developers starting new feature work.
Human QA sessions
Exploratory testing
Plan human QA sessions for risky flows, accessibility issues, and mobile behavior that automation can miss.
Use case
Use this for manual QA sessions before release.
Best for
Manual testers, QA leads, and teams preparing a release pass.
Use case
Use this for basic accessibility validation of a page, form, modal, or feature.
Best for
Manual testers, QA leads, and teams preparing a release pass.
Use case
Use this for responsive web apps and touch-heavy workflows.
Best for
Manual testers, QA leads, and teams preparing a release pass.
Changed flows and releases
Regression testing
Build regression and end-to-end coverage after existing product flows change.
Use case
Use this after a PR changes an existing flow.
Best for
QA teams reviewing pull requests, deployments, and changed user journeys.
Use case
Use this for full customer journey coverage.
Best for
QA teams reviewing pull requests, deployments, and changed user journeys.
Reports to QA action
Bug triage
Turn bug reports, logs, support tickets, and PRs into clearer reproduction steps and QA action plans.
Use case
Use this when a bug report is messy, vague, or incomplete.
Best for
QA leads, support teams, and engineering teams sorting issue priority.
Use case
Use this for issue triage.
Best for
QA leads, support teams, and engineering teams sorting issue priority.
Use case
Use this when production logs reveal recurring errors.
Best for
QA leads, support teams, and engineering teams sorting issue priority.
Use case
Use this with a diff, PR description, or changed files.
Best for
QA leads, support teams, and engineering teams sorting issue priority.
Use case
Use this when support tickets reveal repeated problems.
Best for
QA leads, support teams, and engineering teams sorting issue priority.
Flows to automated QA
Playwright test generation
Generate browser test scenarios and Playwright TypeScript checks from user flows and acceptance criteria.
Use case
Use this for creating automated browser tests.
Best for
QA automation engineers and coding agents writing maintainable browser tests.
Use case
Use this when you want a direct path from ticket to automation.
Best for
QA automation engineers and coding agents writing maintainable browser tests.
Endpoints and contracts
API testing
Create endpoint-level test cases for contracts, validation, permissions, and error responses.
[ 18 ]
Use case
Use this for REST or GraphQL endpoint testing.
Best for
Backend QA, API owners, and teams validating REST or GraphQL behavior.
Things likely to break
Edge cases
Find negative paths, edge conditions, auth failures, billing risks, and responsive behavior before users do.
[ 19 ]
Use case
Use this when a feature looks simple but may hide risky behavior.
Best for
QA engineers looking beyond the happy path.
[ 20 ]
Use case
Use this to catch validation and error-handling issues.
Best for
QA engineers looking beyond the happy path.
Use case
Use this for SaaS apps with Stripe or subscriptions.
Best for
QA engineers looking beyond the happy path.
Use case
Use this for login, signup, password reset, and sessions.
Best for
QA engineers looking beyond the happy path.
Ship with confidence
Release QA
Prepare release validation checklists for smoke tests, regressions, rollback readiness, and post-release monitoring.
Use case
Use this before shipping a new version.
Best for
QA leads and release owners deciding whether a version is ready to ship.
CI stability
Flaky test debugging
Review unstable Playwright tests for selector, timing, state, and CI reliability problems.
Use case
Use this when your test works locally but fails in CI.
Best for
Automation engineers maintaining reliable CI checks.
Always-on QA
Monitoring checks
Create production and staging smoke tests that catch broken critical flows before customers report them.
Use case
Use this for AlwaysQA scheduled checks.
Best for
Teams using AlwaysQA scheduled checks and continuous QA monitoring.
How to use these prompts
Turn prompts into repeatable QA checks
AlwaysQA is designed for teams that want QA to happen continuously, not only before release.
- 1 Paste the prompt into your AI agent or AlwaysQA-connected workflow.
- 2 Add your product context, URL, ticket, PR, bug report, or logs.
- 3 Let the agent generate the QA plan, test cases, or Playwright checks.
- 4 Review the output like a QA lead.
- 5 Save the most important checks as automated AlwaysQA monitors.
Continuous QA
Let your agent test your app continuously
Connect AlwaysQA to your workflow and turn prompts, tickets, PRs, and user flows into automated QA checks.
Your QA engineer can:
- Generate test scenarios
- Create Playwright checks
- Validate bug reports
- Run smoke tests
- Monitor critical flows
- Report what broke and why