Design the Test Workflow


Go to Jira Administration > Issues > Workflow and design the workflow. 

Here is a simple example that can be used as a Test Execution Workflow. 


If you already have a workflow similar to this one, you can use it. No need to create a new one!

This is just an example. Implement a workflow that is adapted to your own needs.


Recommendations

  • To keep it simple, you can have an initial status (e.g., “new”), another when it’s in progress (e.g., “in progress”) and then another when it’s finished (e.g. “closed”).
  • If your Test Executions needs approval or you have a reviewing state, you can then disallow executions for it, in the Xray settings. 
  • You may need to have an interim status if you need to review the results of a Test Execution. For Test Executions, it may be quite appropriate for both manual and automated testing (due to flaky tests).



Update the Workflow Scheme 

After designing the workflow you need to make it active for your project, you do that by updating the workflow scheme.

Go to your Project > Project settings > Workflows and click  "Add Workflow.  

Then select the workflow and mapped it with the issue types "Test Execution" and " Sub-Test Execution"

Don't forget to publish the scheme after updating!

Update the Workflow Settings in Xray

Go to Jira Administration > Manage Apps > Xray > Miscellaneous and you can: 


  • Disallow executions in certain workflow statuses. For example, it makes sense to disallow it to "Closed" status. 
  • Automatically transition the Test Execution issue when the test run is executed. For example, it makes sense to transition the issue to the status "in progress" when the test starts to be executed. 
  • Automatically transition the Test Execution issue when the test run is in final status. For example, it makes sense to transition the issue to the status "closed"
  • Set a resolution, you can use the default resolution or a specific one, like "Done".



Want to know more about creating and configuring workflows? Check out the Atlassian Documentation.

  • No labels