CI stability

AI prompts: Flaky test debugging

Prompts for reviewing unstable automated checks, weak selectors, timing issues, and test data dependencies.

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.

Review a Playwright test for reliability

Use this when your test works locally but fails in CI.

You are a senior QA automation engineer.
Review this Playwright test and identify why it may be flaky:
[PASTE TEST CODE]

Look for:
- Timing issues
- Weak selectors
- Missing waits
- Race conditions
- Overly broad assertions
- Test data dependencies
- Shared state
- Network instability
- Browser-specific behavior

Return:
1. Problems found
2. Why each problem matters
3. Improved version of the test
4. Additional recommendations for CI stability

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 Flows to automated QA Playwright test generation Endpoints and contracts API testing Things likely to break Edge cases Ship with confidence Release QA Always-on QA Monitoring checks