Page History
Xray uses different issue types for implementing the testing process (with the exception of Test Runs).
That Thus means that you are able to manually log time on those issues , using JIRA Jira out-of-the-box. And if If you have some other apps or integrations that are based on this field, then you are going to have it available there also.
Info | ||
---|---|---|
| ||
Only some issue types have time tracking enabled by default: Test Execution, Test Plan. However, if you want, you can then easily add Time Tracking features to the other issue types (Test, Pre-Condition, Test Set) , by editing the respective view/default screens and add adding the "Time Tracking" field. |
But then the following The question arises: How do I log the time I spent executing some tests runs?.
The time that you spend executing some Test Run is not logged in JIRA Jira automatically; you have to log it manually , normally in the respective corresponding Test Execution issue.
Note that Xray is able to automatically calculate the elapsed time from each Test Run , based on the "Started on" and "Finished on" dates of the Test Run. Some reports (e.g. , Test Runs Report, Test Executions Report) use this value for the calculation of the overall elapsed time or simply display it.
Thus, the elapsed time (which is calculated automatically) and the actual logged time are two different things. You can choose to log exactly the shown displayed elapsed time, to report another value or even not to even log anything.
Table of Contents |
---|
...
The following table presents some possible usage scenarios for logging time in Xray issue types.
Issue type | Purpose | Notes |
---|---|---|
Test | log time |
related to specification | don't log time |
related to execution here because Test issues are like test templates | |
Pre-Condition | log time |
related to specification | |
Test Set | log time |
related to the creation of Test Set, |
eventually considering the time |
related to the specification of related Tests and Pre- |
Conditions | |
(Sub)Test Execution | log time |
related to the execution of related Test runs | |
Test Plan | log time |
related to environment setup, planning | don't log time related to execution twice (both in the Test Plan and in the related Test Executions) |
Possible usage scenarios for using time estimates
The following table presents some possible usage scenarios for using time estimates, through the "Original Estimate" field, in Xray issue types.
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 |
Recommendations
Using time estimates and logging time depends depend on your use case; you . You can choose to use both or just some one of them.
The following are some generic "recommendations" that may or not be applicable to youGeneral recommendations:
- use Use the "Original Estimate" on Test issues to estimate the execution duration, so that you can then afterwards make some calculations based on it;.
- if 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;.
- log Log execution time in Test Executions , right after you finish running a given Test Run based on the elapsed time. In order to To obtain the elapsed time, you can use the Test Runs report. A more seamless way may be implemented in the near future.