Page History
Since Xray uses issue types in order to map the different testing entities, you're can take advantage of it in order to implement workflow mechanisms.
This is unique and powerful because it allows you to have full control of your testing process, by controlling the transition of statuses in these issue types.
You can then also invoke post-functions when certain statuses are met, such as notifying certain stakeholders or generate highly detailed reports; this can be quite useful.
The following table summarizes some possible aims for implementing JIRA workflows on top of Xray issue types.
...
Issue Type | Workflow usage scenarios |
---|---|
Pre-Condition |
|
Test |
|
Test Set |
|
Test Execution |
|
Test Plan |
|
Using JIRA workflows is not mandatory but they can be used to enhance your process. Some general recommendations on using workflows though:
- Don’t overcomplicate the workflows but respect your internal process
- Add "reviewing statuses” where appropriate (at specification and execution)
- Define a global workflows for your test related issues and also for your requirements
...