Test Case Block
Document individual test cases with preconditions, step-by-step actions, expected results, and execution status tracking.
The Test Case block documents individual test cases with structured steps, expected results, and execution tracking. It supports priority levels, status tracking, and assignee management.
When to Use
Block Properties
| Property | Required | Description |
|---|---|---|
| Test ID | No | Unique identifier (e.g., TC-001) |
| Title | Yes | Name of the test case |
| Description | No | What the test verifies |
| Preconditions | No | Setup required before execution |
| Steps | No | Ordered actions with expected results |
| Postconditions | No | Expected state after execution |
| Priority | No | Critical, High, Medium, Low |
| Status | No | Draft, Ready, Passed, Failed, Blocked, Skipped |
| Assignee | No | Person or team responsible |
Test Status Values
Example: Passed Test Case
A login verification test that has passed.
Example: Failed Test Case
A test case that discovered a defect.
Example: Ready for Execution
A test case prepared but not yet executed.
Best Practices
| Practice | Description |
|---|---|
| Specific Expected Results | Write clear, specific expected results |
| Single Verification Per Step | Include only one verification per step |
| Explicit Preconditions | Document all preconditions explicitly |
| Consistent Naming | Use consistent naming conventions for test IDs |
| Requirement Links | Link test cases to requirements |
| Atomic Steps | Keep steps atomic and independently verifiable |