#Viewing Test Run Details - Properties Guide

#Viewing Test Run Details

#To view test run details:

1. Click on any test run row in the table
2. The test run details view opens, showing:

Test Run Information:

• Title and description
• Status and progress
• Custom fields
• Test case count and completion

Test Cases List:

• All test cases in the test run
• Test case status (Passed, Failed, Blocked, Skipped, Not Executed)
• Assigned users
• Test case details and results

Filters:

• Filter test cases by status, priority, severity, type
• Filter by assigned user
• Search test cases

#Test Run Properties

Each test run has the following properties:

• Test Run ID: Unique identifier for the test run
• Title: Name of the test run
• Description: Brief summary
• Status: Overall status (Not Started, In Progress, Completed)
• Project: Project the test run belongs to
• Test Cases: List of test cases in the test run
• Test Case Statuses: Distribution of test case statuses
• Completion Percentage: Percentage of completed test cases
• Created Date: When the test run was created
• Updated Date: When the test run was last modified
• Created By: User who created the test run
• Custom Fields: Project-specific fields

#Understanding Test Run Status

#Status Calculation

Test run status is calculated based on test case execution:

• Not Started: No test cases have been executed (all are “Not Executed”)
• In Progress: Some test cases have been executed, but not all
• Completed: All test cases have been executed (none are “Not Executed”)

#Progress Tracking

The progress bar shows:

• Visual Representation: Color-coded bars showing status distribution
• Completion Count: Number of completed test cases vs total
• Status Breakdown: Visual breakdown of Passed, Failed, Blocked, Skipped, Not Executed

#Test Case Sources

Test cases in a test run can come from multiple sources:

• Manual Selection: Explicitly selected test cases
• Requirements: Test cases linked to selected requirements
• Test Suites: Test cases included in selected test suites

Each test case shows badges indicating its source, helping you understand where test cases came from.

#Test Runs vs Releases

#Test Runs

• Independent: Can be created independently
• Flexible: Can include any test cases
• Quick Execution: For ad-hoc or quick testing
• Single Execution: Typically run once

#Releases

• Structured: Part of release planning
• Timeline-Based: Has start and end dates
• Multiple Executions: Can contain multiple test runs
• Release Context: Tied to specific project versions

Note: Test runs can be created within releases or independently, depending on your workflow.