Executing Test Cases - Recording Results Guide
Executing test cases is the core of the testing process. During execution, you run each test step, record its outcome, capture evidence, and document observations directly at the step level to ensure accurate and traceable results.
Executing Test Cases
- Open the Test Run details
- Click on a test case from the list
- The Test Case Execution View opens
- Review the test case steps and expected results
- Execute the test steps
- Record execution results and step-level notes
- Save the execution
Execution Workflow
A typical execution flow looks like this:
-
Select Test Case
Open a test case from the test run list. -
Review Test Details
Review preconditions, steps, expected results, and attachments. -
Execute Steps
Perform each step as defined. -
Record Step Results
Record outcomes and observations per step. -
Save Execution
Save the test case execution status.
Recording Execution Results
At the test case level, choose one of the following statuses:
- Passed – All steps executed successfully
- Failed – One or more steps failed
- Blocked – Execution could not proceed
- Skipped – Test case intentionally skipped
- Not Executed – Default state before execution
Step-Level Execution Notes
Execution notes are captured per test step, not as global comments.
For each step, you can:
- Add execution notes describing:
- What actually happened
- Observed behavior
- Differences from expected result
- Attach files such as screenshots or logs
- Update notes independently for each step
Step notes are especially useful for:
- Diagnosing failures
- Capturing partial success or unexpected behavior
- Providing context without cluttering the entire test case
Step Result Scenarios
Passed Step
- Step behaved as expected
- Optional note can be added for clarity
Failed Step
- Step did not produce expected result
- Add:
- Failure description
- Observed output
- Supporting attachments (recommended)
Blocked Step
- Step could not be executed
- Add clear blocking reason
- Example:
- Dependency unavailable
- Environment issue
- Previous step failure
Skipped Step
- Step intentionally skipped
- Add reason for skipping
Attachments During Execution
Attachments can be added at the step level:
- Screenshots
- Videos
- Logs
- Supporting documents
Attachments are stored alongside the step execution and help provide concrete evidence for results.
Updating Execution Status
Execution results can be updated:
- During execution — while running the test
- After execution — if corrections are required (with permission)
- In bulk — for multiple test cases
Bulk Status Updates
- Select multiple test cases
- Choose a status from bulk actions
- Apply the update
Bulk updates are useful when:
- Environment issues block multiple tests
- Skipping out-of-scope tests
- Finalizing execution results
Assigning Test Cases
Assignments help distribute execution work.
Assigning Test Cases
- Select one or more test cases
- Use the assignment picker
- Assign users
- Changes are saved immediately
Bulk Assignment
- Assign multiple test cases at once
- Useful for parallel execution and workload distribution
Execution Best Practices
Step-Level Documentation
- Always document failed or blocked steps
- Be specific and factual
- Avoid vague notes like “didn’t work”
- Include environment or configuration details when relevant
Status Accuracy
- Choose the correct test case status
- Do not mark Passed if any step failed
- Always add reasons for Blocked or Skipped steps
Execution Review
Before completing a test run:
- Review failed and blocked steps
- Ensure notes and attachments are present where needed
- Confirm execution statuses reflect actual outcomes
Key Design Principle
Execution notes live with the step, not as global comments.
This ensures:
- Clear traceability
- Reduced noise
- Better debugging context
- Scalable execution history
Next Steps
- Review Best Practices for Test Runs
- Understand how executions differ from Executions in Releases