Page History
| Table of Contents |
|---|
Xray uses different issue types for implementing the testing process (with the exception of Test Runs).
...
| Issue type | Purpose | Notes |
|---|---|---|
| Test |
| using "estimated execution time" may be more adequate; however if you choose that approach, you may have to decide where to report the estimation for the specification (e.g. in a Test Set or in some specificaiton task) |
| Pre-Condition |
| see notes for Test issue |
| Test Set | estimated time for specifying all the Tests being grouped within this Test Set | |
| (Sub)Test Execution | estimated time for running all related Test Runs | |
| Test Plan |
| your estimated time aim for the Test Plan should match the aim of the logged time |
Comparisons
At individual Test Run level, original estimated vs effective elapsed time
For obtaining the elapsed time for each Test Run, you may use the Test Runs Report. Then you may export it to CSV.
You would need however to export also Test issues from the Issue search page and show the "Original Estimate" field. Then you could cross the two results in order to have a one-to-one comparison.
At Test Execution level, comparing the sum of the estimated times for each Test vs the sum of the elapsed time for all the Test Runs
In this case we compare estimations on Test issues against the actual elapsed time (not the logged time/work logs on the Test Execution).
In order to obtain the "the sum of the estimated times for the Tests that are part of the Test Execution", we can either do an Issue Search based on the Tests and show the Original Estimate column, or we can use an additional add-on to build a calculated custom field. sumUp add-on is a good solution for that.
With "sumUp" you may define a rule and then you can use a custom field which calculates the value based on it.
a) create a configuration
b) create a custom field (e.g. "TestsEstimation") of type "SumUp Text" and configure it to use the "Estimation" created previously; associate it to the Test Execution screens
Then in Issues search page, that information can be seen as a column.
In order to obtain the sum of the elapsed time, you may use the "Test Executions Report", which you can export to CSV if you wish to cross the values.
At Test Execution level, comparing the sum of the estimated times for each Test vs the sum of the logged time (work logs)
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) for creating a calculated custom field with its value.
We can then just compare that value of that custom field (e.g. "TestsEstimation") to the "Time Spent" directly.
If you prefer to use estimation on the Test Execution field, you may use the "TestsEstimation" as an auxiliary field for filling out the value of the "Original Estimate" on the Test Execution. Then you can use the standard "Original Estimate" vs "Time Spent" comparisons.
Recommendations
Using time estimates and logging time depend on your use case. You can choose to use both or just one of them.
...