Running Tests
Running tests is the shared workflow used by both release executions and standalone test runs.
During testing, users open a selected test case, review its steps, record the result, and capture notes or evidence at the step where the observation happened.
Open A Test Case
To run a test case:
- Open an execution or test run.
- Select a test case from the list.
- Review the test case details.
- Perform the test steps.
- Record the test case result.
- Add notes or attachments where needed.
- Save the result.
Before recording a result, review the available test case information, including preconditions, steps, expected results, and attachments.
Test Case Results
At the test case level, choose one result:
- Passed: the test case worked as expected.
- Failed: one or more steps did not work as expected.
- Blocked: testing could not continue.
- Skipped: the test case was intentionally skipped.
- Not Executed: the test case has not been run yet.
Use Failed when the product behavior does not match the expected result. Use Blocked when the tester cannot proceed because of an environment, dependency, access, data, or setup issue.
Step-Level Results
Each test step can have its own result and notes.
Use step-level results to show exactly where testing passed, failed, became blocked, or was skipped.
Use step-level notes to explain:
- What actually happened.
- Which expected result was not met.
- Why the step could not continue.
- Why the step was skipped.
- What evidence is attached.
Attach Evidence
Attachments can be added at the step level. This keeps proof close to the step where it matters.
Helpful attachments include:
- Screenshots
- Logs
- Videos
- Supporting files
Attach evidence for failed and blocked steps whenever possible. Evidence helps reviewers understand the issue without repeating the test.
Assign Test Cases
Assignments help teams split execution work across users.
Users can assign individual test cases or select multiple test cases and assign them together. Assignment information is used in analysis views to show remaining work and ownership.
Bulk Updates
Where available, bulk updates help change multiple selected test cases at once.
Use bulk updates when:
- A shared environment issue blocks several tests.
- A group of tests is intentionally skipped.
- A set of test cases should be assigned to one user.
- A group of related tests has the same result.
Review the selected test cases before applying a bulk update. Bulk changes should reflect real testing outcomes, not just cleanup.
Review Results During Testing
As testing progresses, review:
- Failed test cases that need defect links.
- Blocked test cases that need unblock action.
- Skipped test cases that need a clear reason.
- Not executed test cases that still need owners.
- Assigned work that has not moved recently.
Use analysis views to spot trends before the end of the execution or test run.
Good Execution Notes
Strong notes are:
- Specific
- Factual
- Written at the affected step
- Paired with evidence when helpful
- Clear enough for someone else to understand later
Avoid vague notes such as “does not work.” Describe the observed behavior, expected behavior, and any conditions that affected the test.
Related Guides
- Learn about Release Executions
- Learn about Test Runs
- Review Execution Analysis
- Review Defect Insights
- Review Defects