Things likely to break

AI prompts: Edge cases

Prompts for finding risky states, invalid paths, and real-world behavior that happy-path testing often misses.

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.

Find missing edge cases

Use this when a feature looks simple but may hide risky behavior.

You are a QA engineer specialized in edge-case discovery.
Analyze this feature and find the edge cases most likely to break in production:
[PASTE FEATURE / FLOW / REQUIREMENTS]

Focus on:
- Empty states
- Invalid input
- Long input
- Special characters
- Slow network
- Duplicate actions
- User refreshes page mid-flow
- Back button behavior
- Permission changes
- Expired sessions
- Race conditions
- Mobile layout issues
- Third-party API failures

Return a prioritized edge-case checklist.

Generate negative test cases

Use this to catch validation and error-handling issues.

You are a QA engineer focused on negative testing.
Generate negative test cases for this flow:
[DESCRIBE FLOW]

Focus on:
- Invalid input
- Missing input
- Wrong permissions
- Expired session
- Duplicate submission
- Network failure
- API timeout
- Upload failure
- Browser refresh
- User cancels action
- Conflicting state

Return test cases with:
- Steps
- Expected error message or behavior
- Severity if broken

Generate payment and billing QA tests

Use this for SaaS apps with Stripe or subscriptions.

You are a QA engineer testing SaaS billing.
Create test cases for this billing flow:
[DESCRIBE BILLING FLOW]

Include:
- New subscription
- Plan upgrade
- Plan downgrade
- Failed payment
- Cancel subscription
- Resume subscription
- Invoice generation
- Trial ending
- Coupon or discount
- Tax/VAT behavior
- Permission checks
- Webhook failure scenarios

Return:
1. Functional test cases
2. Edge cases
3. Regression risks
4. Suggested automated checks
5. Manual checks that require payment-provider dashboard verification

Create QA checks for authentication

Use this for login, signup, password reset, and sessions.

You are a QA engineer testing authentication.
Create a test suite for the following authentication flow:
[DESCRIBE AUTH FLOW]

Include:
- Signup
- Login
- Logout
- Password reset
- Email verification
- Expired token
- Invalid credentials
- Account lockout if relevant
- Session expiration
- Multi-device behavior
- Role-based access
- Direct URL access without permission

Return a structured checklist with automation priority.

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 Ship with confidence Release QA CI stability Flaky test debugging Always-on QA Monitoring checks