Development

Generate high-value test cases for features

Design and prioritize normal, boundary, exception, permission and concurrency scenarios based on behavioral contracts.

Complete prompt

You are a risk-focused test engineer. Please design a test plan for the following functionality.

Functional requirements: [Requirements or user stories]
Technology stack: [technology stack]
Existing implementation or interface: [Code or interface (optional)]
Test level: [Unit testing / Integration testing / End-to-end / All]

First refine the verifiable behavioral contract, and then output the test case table according to priority: scenarios, preconditions, inputs, operations, expected results, test levels, and risk levels.

Must cover normal flow, boundary values, null values, illegal input, permissions, repeated requests, timeouts, dependency failures, concurrency and data consistency. Finally point out tests that are not worth automating and requirements information that is still missing.

Example output

P0｜Expired discount code｜Input: code that expired yesterday｜Expected: application rejected and order amount unchanged
P0｜Concurrent reuse｜Two requests use limited-time coupons at the same time｜Expected: only one succeeds
P1｜Discount exceeds order amount｜Expected: minimum amount payable is 0

USAGE GUIDE

When to use it

Design and prioritize normal, boundary, exception, permission and concurrency scenarios based on behavioral contracts. Use it as a structured starting point, then review the result against your original material.

How to fill the variables

Requirements or user stories: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
technology stack: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
Code or interface (optional): Add concrete facts, context, and constraints. Mark unknown details instead of guessing.
Unit testing / Integration testing / End-to-end / All: Add concrete facts, context, and constraints. Mark unknown details instead of guessing.

Get better results

Describe the audience and intended decision.
Include source material and hard constraints.
State what the model must not invent.

Before you use the output

Verify facts, numbers, and quotations.
Check that uncertainty is clearly labeled.
Test or review high-impact recommendations.

Editorial note: This template has been structured for practical use. Results vary by model and input; verify important outputs against primary sources.