![]() ![]() Then in Issues search page, that information can be seen as a column. "TestsEstimation") of type "SumUp Text" and configure it to use the "Estimation" created previously associate it to the Test Execution screens ![]() With "sumUp" you may define a rule and then you can use a custom field which calculates the value based on it.ī) create a custom field (e.g. sumUp add-on is a good solution for that. 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. In this case we compare estimations on Test issues against the actual elapsed time (not the logged time/work logs on the Test Execution). 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 Then you could cross the two results in order to have a one-to-one comparison. ![]() You would need however to export also Test issues from the Issue search page and show the "Original Estimate" field. Your estimated time aim for the Test Plan should match the aim of the logged timeĬomparisons At individual Test Run level, original estimated vs effective elapsed timeįor obtaining the elapsed time for each Test Run, you may use the Test Runs Report. estimated time for all the effort associated with the validation of the Tests within the plan, including environment setup and multiple iterations.estimated time related only with environment setup, planning.estimated specification time for this Pre-ConditionĮstimated time for specifying all the Tests being grouped within this Test SetĮstimated time for running all related Test Runs.estimated execution duration for this Pre-Condition.in a Test Set or in some specification task) ![]() 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. estimated specification time for this Test.estimated execution duration for this Test.You can choose to log exactly the displayed elapsed time, report another value or not even log anything. Thus, the elapsed time (which is calculated automatically) and the actual logged time are two different things. 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. 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. The time that you spend executing some Test Run is not logged in Jira automatically you have to log it manually in the corresponding Test Execution issue. The question arises: How do I log the time I spent executing some tests runs?. However, 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 adding the "Time Tracking" field. Only some issue types have time tracking enabled by default: Test Execution, Test Plan. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |