Test Case
A Test Case checks one behavior or risk. It names the starting setup, action, and expected result.
Another example
A password reset uses an expired link and submits a new password. It expects no account change and shows a safe recovery message.
Main parts
- 01Code or behavior under test
- 02Observable evidence
- 03Coverage, failure, and recovery
Use it when
Use it for important behavior that must be repeatable. State setup, data, steps, and result.
Do not use it when
Do not write vague cases like “test login.” Avoid code details and unrelated checks.
Name used in code
Given setup → When action → Then observation Before you ship
Check the environment and prepared test data (fixture). Define a result you can observe, failure and edge cases, isolation, stable inputs, useful error details, and cleanup. Set a time budget, owner, and flaky-test rule.
Outcome: Use Test Case to gather repeatable evidence about this behavior or quality risk. User context: A password reset uses an expired link and submits a new password. It expects no account change and shows a safe recovery message. Validation approach: Test Case. Why it fits: Use it for important behavior that must be repeatable. State setup, data, steps, and result. Do not use it when: Do not write vague cases like “test login.” Avoid code details and unrelated checks. Test requirements: Name the system and test environment. Define prepared test data, other inputs, and the result you can observe. Include failure and edge cases, allowed error, isolation, and cleanup. Test operations: Make failures easy to diagnose. Control random or changing inputs. Name an owner. Keep the test fast and simple enough for its release gate. Acceptance criteria: The test fails for the known bug and passes after the fix. It repeats in the target environment, gives useful evidence, and does not expose or change unrelated data. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Release gate, environment, prepared test data, allowed error, time budget, owner, and flaky-test rule.
Check this request
Review the current use of Test Case. Definition: A Test Case checks one behavior or risk. It names the starting setup, action, and expected result. Release checks: Check the environment and prepared test data (fixture). Define a result you can observe, failure and edge cases, isolation, stable inputs, useful error details, and cleanup. Set a time budget, owner, and flaky-test rule. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.