#Executing Test Cases - Recording Results Guide

#Executing Test Cases

To execute a test case:

1. Open the test run details
2. Click on a test case in the list
3. The test case execution view opens
4. Review test case steps and expected results
5. Execute the test case and record results:
   • Pass: Test case passed
   • Fail: Test case failed (add failure details)
   • Block: Test case is blocked (add blocking reason)
   • Skip: Skip this test case
6. Add comments and attachments if needed
7. Save the result

#Execution Process

1. Select Test Case: Click on a test case in the test run
2. Review Details: Review test case steps and expected results
3. Execute: Perform the test steps
4. Record Result: Select status and add details:
   • Passed: Test passed, add any notes
   • Failed: Test failed, add failure details and steps to reproduce
   • Blocked: Test is blocked, add blocking reason
   • Skipped: Skip test, add skip reason
5. Add Attachments: Upload screenshots or files if needed
6. Add Comments: Add execution notes or observations
7. Save: Save the execution result

#Test Case Status Updates

Test case status can be updated:

• During execution (when recording results)
• After execution (to change status if needed)
• In bulk (select multiple test cases and update status)

#Assigning Test Cases

To assign test cases:

1. Select one or more test cases
2. Click Assign or use the assignment picker
3. Select users to assign test cases to
4. Test cases are assigned and users are notified

Bulk Assignment:

• Select multiple test cases
• Assign them all to one or more users
• Useful for distributing work across team members

#Assignment and Collaboration

• Assign Test Cases: Assign test cases to team members
• View Assignments: See who is assigned to which test cases
• Reassign: Change assignments as needed
• Comments: Add comments for collaboration

#Test Case Execution Tips

#Recording Results

• Be Detailed: Add detailed notes for failed tests
• Include Screenshots: Attach screenshots for visual issues
• Document Steps: Record steps to reproduce failures
• Add Context: Include environment and configuration details

#Status Management

• Update Regularly: Keep test case status current
• Use Appropriate Status: Choose the correct status (Passed, Failed, Blocked, Skipped)
• Document Reasons: Always add reasons for Blocked or Skipped statuses
• Review Before Completing: Review all test cases before marking test run as complete

#Collaboration

• Assign Appropriately: Assign test cases to qualified team members
• Communicate: Use comments to communicate issues or questions
• Share Information: Share execution notes and findings
• Coordinate: Coordinate with team members on shared test runs