Flows to automated QA

AI prompts: Playwright test generation

Prompts for generating and improving Playwright tests from user flows, tickets, and acceptance criteria.

Data security: Use these prompts with your coding agent or QA workflow. Avoid pasting secrets, credentials, or sensitive customer data into tools you do not control.

Generate Playwright tests from a user flow

Use this for creating automated browser tests.

You are a senior QA automation engineer.
Create Playwright tests for this user flow:

Application URL:
[URL]

User flow:
[DESCRIBE USER FLOW]

Test data:
[ADD TEST DATA IF AVAILABLE]

Requirements:
- Use stable selectors where possible
- Avoid testing implementation details
- Include assertions after each important step
- Include negative cases if relevant
- Make the test readable and maintainable
- Add comments only where helpful

Return:
1. Test scenarios
2. Playwright test code in TypeScript
3. Required test data
4. Any assumptions

Generate Playwright tests from acceptance criteria

Use this when you want a direct path from ticket to automation.

You are a QA automation engineer.
Generate Playwright tests from these acceptance criteria:
[PASTE ACCEPTANCE CRITERIA]

Application context:
[DESCRIBE APP / PAGE / USER ROLE]

Return:
- Test file structure
- Test names
- Playwright TypeScript code
- Assertions
- Recommended selectors
- Setup and teardown notes
- Cases that should stay manual

Other areas

Requirements to QA coverage Test planning Human QA sessions Exploratory testing Changed flows and releases Regression testing Reports to QA action Bug triage Endpoints and contracts API testing Things likely to break Edge cases Ship with confidence Release QA CI stability Flaky test debugging Always-on QA Monitoring checks