106 AI prompts for testers
Ready-to-use prompts for everyday QA work. Copy one, replace the parts in [brackets] and paste it into Claude, Copilot Chat or any other assistant.
- Give context: paste the real requirement, code or log.
- Check every answer. AI suggests, you decide.
- Never paste customer data, secrets or internal code into tools your company has not approved.
106 prompts
Test ideas
-
01
Risk-based test ideas
You are an experienced software tester. Here is a user story with its acceptance criteria: [paste story] List the 10 riskiest things that could go wrong for real users. For each one, give a one-line test idea and explain why it is risky.
-
02
Exploratory charters
Create 5 exploratory testing charters for [feature]. Use the format "Explore <area> with <resources> to discover <information>". Include one charter about accessibility and one about security.
-
03
Questions before testing
Read this requirement: [paste requirement] List the questions a tester should ask the product owner before testing starts. Group them into: unclear behaviour, missing edge cases, non-functional requirements.
-
04
Heuristic checklist
Apply these heuristics to [feature]: CRUD, boundaries, interruptions, permissions, concurrency. Give me a checklist of concrete checks for this feature, not general advice.
-
05
Personas
Describe 4 different user personas for [product]. For each, list 3 ways they could use [feature] that a happy-path test would miss.
-
06
What changed?
Here are the release notes / the diff summary: [paste] Which existing features could be affected indirectly? Give me a focused regression list.
-
07
Negative testing
List 12 negative test ideas for [feature]: wrong input, wrong order of actions, missing permissions, lost connection, double submit.
-
08
State transitions
Draw the states and transitions of [object, e.g. order] as a table. Then list tests for every valid transition and 5 invalid ones.
Exploratory testing
-
09
Session plan
Plan a 60-minute exploratory session for [feature]: charter, areas, heuristics to use, and what notes I should take.
-
10
Tour ideas
Suggest 6 exploratory 'tours' (e.g. money tour, landmark tour, back-alley tour) adapted to [product] and what each could reveal.
-
11
Session notes to report
Here are my raw exploratory notes: [paste] Turn them into a short session report: what I tested, bugs, questions, risks, ideas for next time.
-
12
Oracle problems
For [feature], how do I know the result is correct? List possible test oracles: specs, comparable products, consistency, user expectations.
-
13
Usability check
Walk through [flow] as a first-time user. List places where a user could get confused, stuck or make a mistake, with a test idea for each.
-
14
Error handling tour
List every way [feature] could fail (network, server, validation, timeouts). For each, what should the user see and how can I trigger it in a test?
Test cases
-
15
Boundary values
Field: [name]. Rules: [e.g. whole number from 1 to 100, required]. Design test cases with equivalence partitioning and boundary value analysis. Output a table with the columns: input, partition, expected result.
-
16
Decision table
Business rules: [paste rules] Build a decision table that covers every combination of conditions. Then reduce it to the smallest set of test cases that still covers each rule, and explain what you removed.
-
17
Gherkin scenarios
Turn these acceptance criteria into Gherkin scenarios (Given / When / Then): [paste criteria] Use a Scenario Outline with Examples where the same flow runs with different data. Keep UI details out of the steps.
-
18
Review my test cases
Here are my test cases: [paste test cases] Review them like a senior tester: what is missing, what is duplicated, and which expected results are too vague? Suggest concrete improvements.
-
19
Pairwise combinations
Parameters and values: [list] Create a pairwise (all-pairs) set of test combinations and explain how many cases it saves compared with all combinations.
-
20
From user story to tests
User story: [paste]. Write test cases with ID, title, preconditions, steps and expected result. Cover happy path, edge cases and errors.
-
21
Acceptance criteria check
Are these acceptance criteria testable? [paste]. Rewrite each unclear one so it has a measurable expected result.
-
22
Prioritise my tests
Here is my test list: [paste]. Prioritise it by risk (impact x likelihood) and tell me which 20% to run if I only have one hour.
Test data
-
23
Realistic fake data
Generate 15 rows of realistic but fake test data for [entity] with the fields [list fields]. Include valid records, edge cases (long names, special characters, Unicode) and 3 invalid records. Return CSV.
-
24
Edge-case strings
List edge-case inputs for the text field "[field]": empty, whitespace only, very long, Unicode, emoji, right-to-left text, SQL-like and HTML-like strings. For each input, say what problem it can reveal.
-
25
SQL data checks
Database tables: [paste schema] Write SQL queries that check the data after [action], for example: no orphaned records, correct totals, no duplicates. Explain what each query proves.
-
26
Dates and time zones
List test data for date and time handling in [feature]: leap years, month ends, daylight-saving changes, time zones, different locale formats.
-
27
Money and numbers
List test values for amount fields in [feature]: rounding, negative values, zero, currency formats, very large numbers, decimal separators.
-
28
JSON test payloads
Here is a JSON schema / example: [paste]. Generate 5 valid payloads and 8 invalid ones, each breaking exactly one rule. Label the rule.
-
29
Anonymise data
Here is a production-like dataset structure: [fields]. Suggest how to anonymise it for testing while keeping it realistic and keeping relations between tables.
-
30
Data for search
Create test data to check a search feature: exact matches, partial matches, typos, case, accents, special characters, empty results, many results.
API testing
-
31
Contract checks
Here is an OpenAPI spec: [paste] List contract tests: required fields, types, enums, status codes, error format. Point out spec gaps.
-
32
Auth tests
List API tests for authentication and authorisation on [endpoint]: missing token, expired token, wrong role, other user's resource (IDOR).
-
33
Pagination and filters
Write test ideas for an API list endpoint with pagination, sorting and filters: first/last page, page size limits, invalid values, stable ordering.
-
34
Idempotency
How should [POST/PUT endpoint] behave when the same request is sent twice? Write tests for retries, timeouts and duplicates.
-
35
Explain a response
Here is an API response: [paste] What does it tell me, what looks wrong or suspicious, and what should I test next?
-
36
curl to tests
Turn this curl command into a set of automated API tests in [Postman / REST Assured / pytest]: [paste curl]
-
37
Mock a dependency
My service calls [external API]. Show how to mock it for tests with [WireMock / Mock Service Worker / Postman mock] including error responses.
-
38
API error messages
Review these API error responses: [paste]. Are they consistent, helpful and safe (no stack traces or internal details)?
Automation
-
39
A clean Cypress test
Write a Cypress test for this flow: [describe steps] Use data-test attributes as selectors, no fixed waits, and one assertion per behaviour. Briefly explain each part.
-
40
API tests in Postman
Here is an API endpoint: [method, URL, example request and response]. Write Postman tests (pm.test) that check the status code, response time, schema and the key business fields. Add 3 negative cases.
-
41
Fix a flaky test
This automated test fails at random: [paste code and error] List the likely causes of flakiness, most likely first, and show how to fix the most likely one.
-
42
Page Object
Refactor this UI test into the Page Object pattern for [framework]: [paste code] Keep tests readable and selectors in one place.
-
43
Good selectors
Here is an HTML snippet: [paste] Suggest stable selectors for automation and explain why IDs or data-test attributes beat CSS classes or XPath here.
-
44
What to automate
Here is my manual regression list: [paste]. Which cases should be automated first, which stay manual, and why? Consider value, stability and cost.
-
45
Playwright test
Write a Playwright test in TypeScript for [flow]. Use getByRole locators, web-first assertions and no hard waits.
-
46
Test review
Review this automated test like a senior automation engineer: naming, assertions, waits, independence, test data. [paste code]
-
47
Selenium to modern
Convert this Selenium test to [Cypress / Playwright] and explain the main differences: [paste code]
Performance
-
48
Load test plan
Create a load test plan for [system]: goals, user scenarios, load profile (ramp-up, steady, peak), metrics and pass/fail criteria.
-
49
Read the results
Here are load test results: [paste numbers] Explain them in plain language. Where is the bottleneck likely to be and what should I measure next?
-
50
k6 script
Write a k6 script that simulates [N] users doing [scenario], with checks on status and response time and thresholds for p95.
-
51
Frontend performance
List checks for front-end performance of [page]: Core Web Vitals, image sizes, caching, number of requests, third-party scripts.
-
52
Capacity questions
Before performance testing [system], which questions should I ask the team about expected load, data volume and SLAs?
-
53
Slow query
This SQL query is slow: [paste] Explain why it may be slow and suggest indexes or rewrites I can test.
Security basics
-
54
OWASP checklist
Create a short OWASP Top 10 checklist for testing [web app], with one practical test per item that a tester (not a pentester) can run.
-
55
Input attacks
List inputs to check [form] for injection and XSS problems, and what a safe application should do with each. For authorised testing only.
-
56
Session security
List tests for login and session handling: logout, session timeout, password reset, remember-me, multiple devices.
-
57
Secrets in code
Review this code / config for hard-coded secrets or sensitive data: [paste] (Remove real secrets before pasting.)
-
58
Permissions matrix
Roles: [list]. Features: [list]. Build a permission matrix and the tests that prove each role can do only what it should.
-
59
Privacy check
Which personal data does [feature] collect or show? List tests for data minimisation, masking, deletion and consent.
Accessibility
-
60
Keyboard test
Give me a step-by-step keyboard-only test for [page]: focus order, visible focus, traps, skip links, shortcuts.
-
61
Screen reader check
What should a screen reader announce on [component]? List checks for names, roles, states and live regions.
-
62
WCAG quick audit
Create a 15-point WCAG 2.2 AA quick audit for [page] that a tester can do in 30 minutes, with how to check each point.
-
63
Accessible forms
Review this form markup for accessibility problems: [paste HTML] Check labels, errors, required fields and instructions.
-
64
Colour and zoom
List tests for colour contrast, colour-only information, 200% zoom and text spacing on [page].
-
65
Explain to the team
Explain why [accessibility bug] matters to real users in 3 sentences I can put into a bug report.
Mobile & responsive
-
66
Mobile checklist
Create a test checklist for the mobile app [app]: install/update, permissions, offline, interruptions (calls, notifications), orientation, battery saver.
-
67
Device matrix
Help me choose a device and OS test matrix for [app] with a limited budget. Explain the reasoning.
-
68
Responsive web
List responsive-design tests for [page] at common breakpoints: layout, touch targets, menus, images, forms.
-
69
Deep links
List tests for deep links and push notifications in [app]: logged in/out, app closed/open, wrong or old links.
-
70
App store release
What should I test before an app store release of [app]? Give me a release-day checklist.
Bug reports
-
71
A bug report that gets fixed
Rewrite this bug report so that a developer can reproduce it in two minutes: [paste bug report] Use: title, environment, steps, expected result, actual result, severity with a reason. Do not invent facts; mark missing information as [MISSING].
-
72
Read the logs
Here is an error log: [paste log] Explain in plain language what probably failed and which component is involved. Then tell me what to check next to confirm the root cause.
-
73
Severity vs. priority
Here are 5 bugs: [paste bugs] Suggest a severity and a priority for each one, with one sentence explaining the difference, so I can discuss it with the team.
-
74
Find the duplicate
Here is a new bug and a list of open bugs: [paste] Is the new bug a duplicate or related to any of them? Explain.
-
75
Root cause questions
Bug: [description]. Which questions should I ask and which logs or data should I collect to help developers find the root cause?
-
76
Minimal reproduction
These are my long reproduction steps: [paste] Help me find the minimal steps that still reproduce the bug.
-
77
Bug trends
Here is a list of bugs from the last release with component and severity: [paste] Which patterns do you see and what should we test more next time?
-
78
Explain to non-technical people
Explain this bug and its business impact for a product owner in 3 sentences: [paste bug]
CI/CD and releases
-
79
Tests in a pipeline
Write a GitLab CI job that installs dependencies, runs [test command] in the Docker image [image], saves the JUnit report as an artifact and fails the pipeline when tests fail. Explain each line.
-
80
Review a change as a tester
Review this code change from a tester's point of view: [paste diff] What could break? Which tests should be added or updated? What should I check manually?
-
81
Go / no-go summary
Test summary: [passed / failed / blocked counts, open bugs with severity, untested areas]. Prepare a short go/no-go recommendation for the release meeting: risks, conditions for release, and the decisions the team has to make.
-
82
GitHub Actions workflow
Write a GitHub Actions workflow that runs [test command] on every pull request, caches dependencies, uploads the test report and blocks merging on failures.
-
83
Jenkinsfile
Write a declarative Jenkinsfile with stages build, unit tests, API tests, UI tests, publish reports. Run UI tests in parallel.
-
84
Pipeline is too slow
Our pipeline takes [time]. Here is the config: [paste] Suggest ways to make it faster: parallelism, caching, test selection, smaller images.
-
85
Quality gate rules
Suggest quality gate rules for [project]: test pass rate, coverage, critical bugs, static analysis. Explain which ones block a release.
-
86
Dockerise the tests
Write a Dockerfile to run my [framework] tests in a container, and explain how to run it locally and in CI.
Planning & reporting
-
87
Test plan outline
Create a lean test plan for [project]: scope, out of scope, approach, environments, entry/exit criteria, risks, schedule.
-
88
Test strategy
Draft a one-page test strategy for a team building [product] with [team size, release frequency]. Include the test pyramid and responsibilities.
-
89
Daily status
Turn these notes into a short daily test status for the team chat: [paste]
-
90
Metrics that matter
Which test metrics should I report to management for [project] so they help decisions instead of looking busy? Explain each in one line.
-
91
Retrospective
Here is what happened in the last release: [paste] Prepare retrospective questions and 3 improvement ideas for quality.
-
92
Risk register
Create a risk register for testing [project]: risk, impact, likelihood, mitigation, owner.
Testing AI features
-
93
Test an LLM feature
Our product has an AI feature that [does X]. List test ideas for correctness, hallucinations, harmful output, prompt injection and consistency.
-
94
Evaluation set
Help me build an evaluation set of 20 inputs with expected qualities (not exact answers) for the AI feature [feature].
-
95
Prompt injection
List prompt-injection test cases for a chatbot that can [actions], and the expected safe behaviour. For authorised testing only.
-
96
Non-determinism
How do I write automated tests for an AI feature whose answers change every run? Suggest assertions and strategies.
-
97
Bias check
Suggest tests to check the AI feature [feature] for bias across language, gender, region and age, and how to report findings.
-
98
Review AI-generated tests
AI wrote these test cases for me: [paste] Check them critically: what is wrong, missing or invented?
Learning & career
-
99
Learning plan
I'm [background] and want to become a QA engineer in [months]. Make a weekly learning plan with free resources and small practice projects.
-
100
CV review
Review my CV for a junior QA role: [paste, without personal data] Suggest concrete improvements and missing keywords.
-
101
Interview practice
Act as an interviewer for a [junior/mid] QA position. Ask me one question at a time and give feedback on each answer.
-
102
Explain a concept
Explain [testing concept] to me like a new tester, with a real-life example and a short exercise.
-
103
Portfolio project
Suggest 3 portfolio projects that show QA skills (manual, API, automation) and what each should contain.
-
104
ISTQB practice
Ask me 10 ISTQB Foundation-style questions about [chapter/topic], one at a time, and explain the correct answers.
-
105
First 90 days
I just started as a tester in a new team. Make a plan for my first 90 days: what to learn, whom to talk to, quick wins.
-
106
Salary research
Which questions should I ask myself and which public sources should I check to estimate a fair salary for a [role] in [city]?
Want to use AI in your testing every day?
In a consultation we pick the prompts and tools that fit your project and set up a way of working you can trust.