AI prompts for QA testers
A free, copy-ready prompt that turns a user story into structured test cases, and an example agent rule for Playwright, Cypress and Selenium code. Paste the results straight into TestLinkPro.
A prompt and an agent rule you can copy
Copy the prompt into ChatGPT, Claude, Gemini or Copilot and replace the placeholders. Treat the output as a first draft and review it.
TCD-01 · User story → structured test cases
Use when: you have a user story with acceptance criteria and need a first set of test cases quickly.
PromptWrite test cases for the user story below.
<story>
{{USER_STORY_AND_ACCEPTANCE_CRITERIA}}
</story>
Requirements:
- Cover every acceptance criterion with at least one positive and one negative test.
- Add edge cases the criteria don't mention but a real user would hit.
- Output a table with columns: ID (TC-{{MODULE}}-001...), Title, Type (Positive/Negative/Edge), Preconditions, Steps (numbered), Test Data, Expected Result, Priority (Critical/High/Medium/Low), AC covered.
- Expected results must be observable: exact messages, URLs, status codes, DB values.
- After the table, list any acceptance criteria that are ambiguous or untestable and suggest a rewrite.
Example output (excerpt)
| ID | Title | Type | Preconditions | Steps | Test Data | Expected Result | Priority | AC |
|---|---|---|---|---|---|---|---|---|
| TC-RESET-001 | Reset link sent to registered email | Positive | User exists | 1. Open /forgot-password 2. Enter email 3. Click "Send link" | ana@example.com | Message "If an account exists, we've sent a link" shown; email received within 2 min | High | AC1 |
| TC-RESET-004 | Unregistered email gets the same message | Negative | No account for email | Same as TC-RESET-001 | nobody@example.com | Same generic message as TC-RESET-001; no email sent | High | AC1 |
| TC-RESET-007 | Reset link expires after 30 min | Edge | Link generated 31 min ago | Open the link | - | "This link has expired" page with option to request a new one | High | AC3 |
Ambiguous: AC2 "link should be secure" → Suggested rewrite: "Link contains a single-use random token, expires after 30 minutes and becomes invalid after a successful reset."
Example outputs use fictional data. Your results will differ, so always review AI output before you use it.
Cursor rules for Playwright, Cypress and Selenium: the golden rules
From qa-automation-core.mdc, the always-on Cursor rule that the framework-specific rules build on. The same standards are in the Claude Code, Copilot and AGENTS.md files.
- A test must fail when the feature is broken. Never weaken, delete or skip an assertion just to make a test pass.
- If a failure looks like a real product bug, say so and stop. Do not "fix" the test to match broken behaviour.
- No hard waits (
waitForTimeout,sleep,Thread.sleep,cy.wait(<number>)). Wait for a condition instead. - Every test is independent: it creates the data it needs and does not rely on other tests or on execution order.
- No secrets, tokens, passwords or real personal data in code. Read them from environment variables or the config layer.
- Keep tests deterministic: control time, randomness and external services where needed.
Manage these tests in TestLinkPro
TestLinkPro is subscription test-management software for QA teams: test cases, test runs, requirements traceability and CI results in one place. Free for up to 5 users, paid plans from $19 a month.