Page History
...
The typical testing lifecyle follows a set of phases that may not be exactly sequential.
For sure, you will be starting start by specifying the requirements for your project. Normally those , these requirements will need to be reviewed and either approved/rejected. From that moment onwardsby stakeholders. Once approved, you are able to start planning, writing and organizing your tests.
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Xray for JIRA allows you to follow this model very closely, however but how will you materialize implement it exactly will be up to you.
With Xray you have the possibility to either You may adopt a very simple, straightforward test or a complete test process implementing all the typical full-blown, comprehensive process that includes all phases of the testing lifecycle.
Therefore, which process should you adopt? We may give you some clues by showing some the possibilities you have.
Test Processes
Complete
Xray allows you to plan, design and execute tests, and also make as well as generate test reporting. It uses specific JIRA Jira issues for most of them.
For each of the testing phasesphase, you would use the following issues:
- Plan phase: Test Plan issues
- Design phase: The specification can be done with Pre-Condition and Test issue types. The organisation organization of the tests can be done using Test Sets.
- Execute phase: Test Execution issues
- Report phase: Test Execution issues, along with the built-in requirement coverage reports and some custom ones using JIRA gadgetsJira tools
Complete (
...
legacy
...
)
Before Xray v2, there was no specific Test Plan issue, though you could implement your "test plan" in one of two ways:
- just by creating Test Executions and consider considering them as your "test plan" for a given version (this had the limitation was that you 'll end up with multiple Test Executions, mostly with the same tests, and missing a consolidated view of your "test plan")
- or, by creating Test Sets; you could define one or more Test Sets for a given version using the fixVersion attribute
Complete
,(with workflows)
This is a variant of similar to the previous approaches, but allows the complete control of the test management workflow.
Maybe you want to validate and approve Test-related issues before using them. Whatever workflow fits best to your organization/scenario the best, you are able to fully manage your testing lifecycle using JIRAJira's workflow facilities for Xray's issue types.
Please find bellow Below is an example of a possible workflow for Test, Pre-Condition or Test Set issues.
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Note that Xray does not not install any workflow, but it is workflow-aware, providing some configurations specificaly specifically for that purpose (see Global Preferences page), . .
| Info | ||
|---|---|---|
| ||
Please have a look at Using JIRA Go to Using Jira workflows for testing purposes, for a more in-depth explanation of the advantages of using JIRA workflows for Xray issue types, along with some usage examples. |
...
Simplest
So you have a small project and just want to add tests to it? This is far not the best option but it may be enough for you. In this case you may You may just use Test issues to create tests for your requirements and execute ad - hoc, unplanned , Test Executions.
This is not the best option, but it may be enough for your needs.