Changed flows and releases

AI prompts: Regression testing

Prompts for regression coverage after product changes, release validation, and full SaaS journey testing.

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 regression tests for a changed feature

Use this after a PR changes an existing flow.

You are a QA engineer reviewing a product change.

The following feature was changed:
[DESCRIBE CHANGE]

Existing behavior before the change:
[DESCRIBE OLD BEHAVIOR]

New expected behavior:
[DESCRIBE NEW BEHAVIOR]

Create a regression test checklist that verifies:
1. The new behavior works
2. The old valid behavior did not break
3. Related flows still work
4. Data is not corrupted
5. Existing users are not affected
6. Error states still work correctly

Mark each test as:
- Must automate
- Manual only
- Optional

Create end-to-end tests for a SaaS application

Use this for full customer journey coverage.

You are a QA lead.
Create an end-to-end test suite for a SaaS application with the following flows:
[LIST FLOWS, FOR EXAMPLE: SIGNUP, LOGIN, BILLING, DASHBOARD, EXPORT, INVITE USER]

For each flow, include:
- Happy path
- Negative path
- Edge cases
- Permissions
- Data validation
- Regression risks
- Suggested automation priority

Also suggest which tests should run:
- On every PR
- On every deployment
- Daily
- Before major release

Other areas

Requirements to QA coverage Test planning Human QA sessions Exploratory 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 CI stability Flaky test debugging Always-on QA Monitoring checks