AI Test Case Generation: 15 Prompts That Actually Work for Testers

Act as a senior software test analyst.

Analyse the following user story and acceptance criteria:

[PASTE USER STORY]

[PASTE ACCEPTANCE CRITERIA]

Create a comprehensive list of test scenarios covering:

1. Happy paths
2. Negative scenarios
3. Boundary conditions
4. Validation rules
5. Business rules
6. Alternate user journeys
7. Error handling
8. Permission and access considerations
9. Data-related scenarios
10. Integration impacts

For each scenario provide:

- Scenario ID
- Scenario description
- Priority: High / Medium / Low
- Risk addressed
- Requirement or acceptance criterion covered

Do not create detailed test steps yet.
Focus first on meaningful test coverage and avoid duplicate scenarios.

Act as an experienced functional test analyst.

Using the test scenario below, create detailed test cases.

TEST SCENARIO:
[PASTE SCENARIO]

Create test cases covering positive, negative and boundary conditions.

For every test case provide:

- Test Case ID
- Test Case Title
- Preconditions
- Test Data
- Step-by-step actions
- Expected Result for every step
- Priority
- Risk
- Requirement / Acceptance Criterion
- Test Type

Do not assume missing business rules.
Clearly identify any assumptions you make.

Act as an independent senior QA reviewer.

Review the following requirements and existing test scenarios.

REQUIREMENTS:
[PASTE REQUIREMENTS]

EXISTING TEST SCENARIOS:
[PASTE SCENARIOS]

Identify test coverage gaps.

Look specifically for:

- Missing happy paths
- Negative paths
- Boundary conditions
- Validation rules
- Business rules
- Permission issues
- Data combinations
- Error handling
- Integration failures
- Concurrency or duplicate actions
- Retry behaviour
- Session or timeout behaviour
- Downstream system impacts

For each gap explain:

1. What is missing
2. Why it matters
3. Suggested test scenario
4. Risk if it is not tested

Do not repeat scenarios that are already adequately covered.

Act as a hostile but realistic software tester.

Analyse this feature:

[DESCRIBE FEATURE]

Generate negative test scenarios designed to make the feature fail.

Consider:

- Invalid input
- Missing input
- Incorrect format
- Unexpected values
- Boundary values
- Duplicate requests
- Incorrect user permissions
- Expired sessions
- Network failures
- Downstream failures
- Invalid state transitions
- Interrupted transactions
- Concurrent actions
- Incorrect sequencing
- Large or unusual data

For each scenario provide:

Scenario
Input / condition
Expected system behaviour
Risk
Priority

Focus on realistic production failures rather than unrealistic edge cases.

Act as a senior test analyst specialising in boundary value analysis.

Analyse the following requirement:

[PASTE REQUIREMENT]

Identify all values that have meaningful boundaries.

For each boundary provide:

- Minimum allowed value
- Just below minimum
- Just above minimum
- Maximum allowed value
- Just below maximum
- Just above maximum
- Zero / null where relevant
- Empty value where relevant
- Maximum realistic production value

Explain why each boundary should be tested.

Present the final answer as a concise test-data table.

Convert the following acceptance criteria into executable functional test cases.

ACCEPTANCE CRITERIA:

[PASTE ACCEPTANCE CRITERIA]

For every acceptance criterion:

1. Identify the intended behaviour.
2. Create at least one positive test.
3. Create relevant negative tests.
4. Identify boundary conditions.
5. Identify missing information or ambiguity.

Output:

Test Case ID
Acceptance Criterion
Scenario
Preconditions
Test Data
Steps
Expected Result
Priority
Risk

Do not invent business rules that are not supported by the supplied requirements.

Act as a senior test data analyst.

I need test data for this feature:

[DESCRIBE FEATURE]

Generate representative synthetic test data covering:

- Valid data
- Invalid data
- Boundary data
- Missing data
- Null values
- Duplicate data
- Special characters
- Maximum-length values
- Minimum-length values
- Invalid formats
- Cross-field combinations

Do not use real personal information.

For each data category explain:

Purpose
Example synthetic value
Expected system behaviour
Related test scenario

Analyse the following feature from an authorisation and access-control perspective.

FEATURE:
[DESCRIBE FEATURE]

USER ROLES:
[LIST ROLES]

Generate test scenarios covering:

- Authorised access
- Unauthorised access
- Read permissions
- Create permissions
- Update permissions
- Delete permissions
- Role changes
- Permission changes
- Direct URL access
- API-level access
- Session changes
- Access after logout
- Access to another user's data

For each scenario provide:

Role
Action
Expected result
Security risk
Priority

Act as an API test specialist.

Analyse this API:

METHOD:
[GET / POST / PUT / DELETE]

ENDPOINT:
[ENDPOINT]

REQUEST:
[REQUEST BODY / PARAMETERS]

EXPECTED RESPONSE:
[RESPONSE]

Generate API test scenarios covering:

- Valid request
- Missing mandatory fields
- Invalid fields
- Invalid data types
- Boundary values
- Invalid authentication
- Missing authentication
- Authorisation
- Duplicate requests
- Unsupported methods
- Invalid content type
- Unexpected parameters
- Error responses
- Response schema validation
- HTTP status codes

For each test include:

Request
Expected status code
Expected response
Validation
Risk

Act as a senior regression test analyst.

A change has been introduced:

[DESCRIBE CHANGE]

Existing functionality includes:

[LIST RELATED FUNCTIONALITY]

Identify regression test coverage that should be considered.

Group scenarios into:

1. Direct impact
2. Indirect impact
3. Integration impact
4. Data impact
5. User journey impact
6. Security / permission impact
7. Reporting impact

For every suggested regression scenario provide:

Scenario
Reason for inclusion
Risk
Priority
Suggested execution level:
Smoke / Regression / Full Regression

Act as a senior QA analyst performing defect leakage analysis.

PRODUCTION DEFECT:
[PASTE DEFECT]

ROOT CAUSE / INVESTIGATION:
[PASTE DETAILS IF AVAILABLE]

Analyse:

1. Why could this defect have escaped testing?
2. Which test condition was missing?
3. Was the issue functional, data-related, integration-related or environment-related?
4. What regression test should be added?
5. What similar scenarios should also be tested?
6. What requirement or test-design improvement could prevent recurrence?

Create a concise prevention and regression-testing recommendation.

Act as a senior tester reviewing this requirement during refinement.

REQUIREMENT:
[PASTE REQUIREMENT]

Do not rewrite the requirement yet.

Instead identify:

- Ambiguities
- Missing business rules
- Missing validations
- Missing error behaviour
- Missing permission rules
- Missing data requirements
- Missing integration behaviour
- Missing boundary conditions
- Missing non-functional considerations
- Questions that should be answered before development

For every issue explain why it matters to testing.

Finish with a list of questions I should ask the Product Owner or Business Analyst.

Act as an experienced end-to-end test analyst.

Business process:
[DESCRIBE PROCESS]

Systems involved:
[LIST SYSTEMS]

Create realistic end-to-end test journeys covering:

- Standard journey
- Alternate journey
- Failed journey
- Partial completion
- Retry
- Duplicate action
- Data handoff between systems
- Integration failure
- User abandonment
- Session timeout
- Recovery after failure

For each journey provide:

Journey name
Starting condition
Systems involved
Key steps
Expected outcome
Major risks
Recommended test priority

Act as an independent Test Lead reviewing my test cases.

REQUIREMENTS:
[PASTE REQUIREMENTS]

MY TEST CASES:
[PASTE TEST CASES]

Review the test cases for:

- Requirement coverage
- Missing scenarios
- Duplicate scenarios
- Weak expected results
- Missing negative tests
- Missing boundary tests
- Poor test data
- Ambiguous steps
- Incorrect assumptions
- Missing integration coverage
- Missing permission coverage

Do not rewrite everything.

For each issue provide:

Test Case ID
Issue
Why it matters
Recommended improvement
Risk

Preserve valid test cases.

Act as my senior Test Lead.

Your goal is to help me design high-quality functional test coverage.

PROJECT / FEATURE:
[DESCRIBE PROJECT OR FEATURE]

REQUIREMENTS:
[PASTE REQUIREMENTS]

Do not immediately generate test cases.

Work through the following stages:

STAGE 1 — Understand
Summarise the business functionality and identify assumptions.

STAGE 2 — Challenge
Identify ambiguities, missing rules and questions for the BA / Product Owner.

STAGE 3 — Risk
Identify the highest-risk areas.

STAGE 4 — Scenarios
Generate comprehensive test scenarios.

STAGE 5 — Coverage
Identify missing positive, negative, boundary, integration and permission scenarios.

STAGE 6 — Test Cases
Generate detailed test cases for the highest-risk scenarios.

STAGE 7 — Review
Review your own output and identify remaining coverage gaps.

Do not invent requirements.
Clearly distinguish facts, assumptions and recommendations.

Prioritise meaningful coverage over generating a large number of test cases.