Execution Workflow
Required configuration for the execution workflow
How the execution workflow works
The execution workflow is generally used to help you track the total estimated time and total logged times for all test executions in Zephyr Squad. If your administrator has this enabled, when you change any execution status or test step execution status, the workflow will kick off from the initial state and Zephyr Squad will begin to log/capture the time it takes to move from one workflow status to the next. The user or manager is able to define the initial time estimate for the test execution as well.
Required configuration for the execution workflow
Jira Time Tracking should be activated for your Jira projects.
The Time Tracking field should be visible when creating an issue which allows you to provide an estimated time.
Within the general configuration page, the execution workflow should be enabled for the particular project.
If the execution workflow is disabled for a particular project, the execution workflow and estimated time field will not be displayed for the project.
For the ad-hoc test cycle, the workflow and estimated time will not be displayed.
How the execution workflow works
The execution workflow consists of 4 different statuses that distinguish the overall status of work that the test execution is on. The 4 statuses for the execution workflow are the following:
To Do
In Progress
Done
Reopen
The estimated time and logged time are given in a format that provides a combination of weeks, days, hours, etc. (eg. 3w 4d 12h).
The time format should be accepted in the Modify logged time field:
Time Format | Jira | Zephyr |
|---|---|---|
1d 1w 2h 1m | PASS | FAIL |
3m 1d 2w 1h | PASS | FAIL |
2d 2h 1w 3m | PASS | FAIL |
1h 1m 2h 2w | PASS | FAIL |
1w 4h 2w 1m | PASS | FAIL |
2h 4w 1m 2d | PASS | FAIL |
1m 2h | PASS | FAIL |
2m 2h | PASS | FAIL |
2h 4w 1m | PASS | FAIL |
Once a test case is created with an estimated time and it is scheduled for execution in any test cycle that is not the Ad-hoc cycle, the default execution workflow for the test execution will be set to To do.
When you or another user updates the status to In Progress, the estimated time will start. This will display the estimated time which was defined when the test case issue was created. You can change the estimated time at any time as long as the workflow status is not set to Done.
When you or another user clicks and changes the status to Done, all users will not be able to make any changes to the time. The test execution will be “masked” and closed which doesn’t allow users to make changes.
If you want to make changes to the estimated or logged time, you must set the status to Reopen which will then allow you to edit the time(s).
After clicking on Reopen, the execution workflow will essentially restart as if it was In Progress and then from here, you can make any and all changes to the test execution including the time(s).
