As a user, I want to view the actual execution time of a test

Description

Users in Xray Cloud need a dedicated field that displays the total actual time spent on a Test across all executions.

A single Test can be executed multiple times through different Test Executions, and each Test Execution can contain one or more Test Runs. Currently, there is no dedicated field that consolidates and shows the total cumulative execution time spent on that Test.

Users need a reusable field that automatically calculates the sum of all actual execution time spent on the Test, across all related Test Runs and Test Executions. This would improve visibility and make execution effort easier to track.

The field should be available so it can be added to different areas such as:

• Test details screen
• Test Execution details screen
• Test Run details screen

User Friction:

• No single place to see the total time spent on a Test.
• Users must manually review multiple executions and runs to calculate totals.
• Difficult to estimate effort for regression cycles or repeated testing.
• No reusable field for dashboards, reporting, filtering, or automation.
• Poor visibility into high-effort or long-running tests.

Steps to Reproduce:

1. Create and execute a Test multiple times in Xray Cloud.
2. Run the Test through different Test Executions.
3. Open the Test details screen, Test Execution screen, or Test Run screen.
4. Attempt to locate a field showing the total actual time spent across all executions.
5. Observe that no dedicated field exists.

Impact

What Would Improve if Solved:

• Users could instantly see the total execution effort for any Test.
• Better planning for regression cycles and future estimates.
• Easier identification of tests consuming excessive time.
• Improved dashboards, reporting, and automation using execution time data.
• Reduced manual calculations and faster decision-making.

Impact on Stakeholders:

• Easier identification of bottlenecks in test execution
• More accurate reporting and planning
• Insight into performance-heavy tests that may need optimization
• Better predictability of release timelines

Occurs whenever teams need to review execution effort, testing efficiency, or estimate future testing cycles

Current Workaround:

• Manually review each individual Test Run.
• Export reports and calculate totals externally.
• Estimate time spent using execution timestamps.
• Maintain separate spreadsheets for tracking execution effort.

Context & Examples:

Concrete example: A Test has been executed three times:

• Run 1 = 10 mins
• Run 2 = 15 mins
• Run 3 = 20 mins

The user expects a dedicated field to show:

Total Actual Time Spent = 45 mins

Instead, users must manually add each execution duration from separate runs or reports.

Workaround risk: Manual calculations increase the chance of errors, missed executions, and inaccurate estimates when reporting effort or planning future regression cycles.