![]() On the Test Executions List report, or if listing Test Executions issue elswhere, use the "Time Spent" custom field to show the logged time on the Test Execution.Let us first start with the out-of-the-box tools available, both pre-installed and available through Atlassian Marketplace.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 elasped time.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.If you provide 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.Use the "Original Estimate" on Test issues to estimate the execution duration, so that you can make some calculations based on it.You can choose to use both or just one of them. Using time estimates and logging time depend on your use case. Your estimated time aim for the Test Plan should match the aim of the logged time. 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 PreconditionĮstimated time for specifying all the Tests being grouped within this Test SetĮstimated time for running all related Test Runs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |