Page History

...

In this case we assume people log time on the Test Execution issues which we want to compare against the estimations made on the Test issues.

In order to obtain the "the sum of the estimated times for each Test", we can follow the same approach we did in 2) above for creating a calculated custom field with its value.

...

• Use the "Original Estimate" on Test issues to estimate the execution duration, so that you can make some calculations based on it.
• If you're doing testing services, using time estimates for Test Sets may be useful if you want to have an idea of the associated effort of the Tests you aim to implement related with that Test Set.
• The Timer on the execution screen records the elapsed time; you may pause it whenever you need it; this elapsed time is not logged by default, and may be different from the logged time as mentioned ahead.
• Log execution time in Test Executions right after you finish a given Test Run, using the log time shortcut on the Test Run execution screen, which will pick by default the elapsed time recorded with the Timer; you may also log a custom elapsed time.
• On the Test Executions List report, or if listing Test Executions issue issues elsewhere, use the "Time Spent" custom field to show the logged time on the Test Execution.