You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Overview

The typical testing lifecyle follows a set of phases that may not be exactly sequential.

For sure you will be starting by specifying the requirements for your project. Normally those requirements will be reviewed and either approved/rejected. From that moment onwards, you are able to start planning, writing and organizing your tests.

testing_lifecycle

Xray for JIRA allows you to follow this model very closely, however how will you materialize it exactly will be up to you.

With Xray you have the possibility to either adopt a very simple or a complete test process implementing all the typical 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 test reporting.  It uses specific JIRA issues for most of them.

For each of the testing phases, 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 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 gadgets

Complete ("legacy" way)

Before Xray v2, there was no specific Test Plan issue, though you could implement your "test plan" in two ways:

  • just by creating Test Executions and consider them as your "test plan" for a given version (this had the limitation that you'll end up with multiple Test Executions, mostly with the same tests, 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 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, you are able to fully manage your testing lifecycle using JIRA's workflow facilities for Xray's issue types.

Please find bellow an example of  a possible workflow for Test, Pre-Condition or Test Set issues.

test_workflow_example

Note that Xray does not not install any workflow but it is workflow aware, providing some configurations specificaly for that purpose (see Global Preferences page),    .

Simpliest

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 just use Test issues to create tests for your requirements and execute ad-hoc, unplanned, Test Executions.

 

  • No labels