Using X-Ray

Owned by Mike Deskis
Last updated: Jan 10, 2024 by Ioana Kocurova
3 min read

What is X-Ray

X-ray is a management tool in JIRA that requires no configuration from the user. If you are familiar with JIRA, X-Ray should pose no problems as the usage and workflows are the same. The tool can be used both in Feature Sprints and during UAT.

X-ray helps with a set of issues:

  • Create and store test cases and make them visible for the team

  • Link test cases to user stories

  • Organize test cases into test sets

  • Communicate easily with the team

  • Organize, create, store test results, report bugs, generate reports

  • Clone existing test cases and make UAT test cases from them

  • Distribute tests to different testers during UAT

  • Easily see the testing progress (what was tested and what was the result)

  • Link bugs to test cases so it is clear why test failed

You can learn more by checking the official site and documentation here.

X-Ray New issue types in JIRA

Test = test case with details
Test Plan = define the scope of testing, contain all Tests tested in the project
Test Set = group of Tests created for testing the same purpose, we usually don’t use it
Test Execution = group of Tests ready for test execution, there should be one Test execution for each Feature Sprint or for every tester in UAT phase
Precondition = can specify in details preconditions for Tests, we usually don’t use it
Sub Test Execution = similar like Test Execution, we usually don’t use it

Demo test cases were created in Test QA project in our JIRA:

The demos includes:

  • Basic overview of issue types

  • How to start with testing on the project

  • How to create test cases from User Stories

  • How to execute test cases and report the results

  • How to see test progress and test results

  • How to see bugs linked to failed test cases

Test Plan:

image-20240110-080614.png

User acceptance testing (UAT) involves test planning and test execution to ensure that the software meets the requirements of end users. In test planning, test scenarios are identified, test cases are defined, and priorities are set. Resources are allocated, and a test plan is documented. During test execution, the testing environment is set up, test data is prepared, and test cases are executed. Any defects found are reported.

Test Executions:

Testing Board: Check it out here. See folder UAT demo test cases at the beginning of the list. Open the folder to check out dedicated use cases.

Alternatively, you can check out out sample UAT test cases in the dedicated Excel file in Downloads.

Tips for the project

To make sure that your project runs as smoothly as possible, here are some tips we have learned after extensive testing. Implement them into your projects to ensure the most efficient process you can.

  • Create a test plan and decide a test strategy

  • Create test cases from user stories – Issue Type is Test and steps should be written to Description field

  • Don’t use Test steps as it will simplify project administration

  • Start with positive scenarios, then add important negative ones

  • Use import of test cases and test steps if you have previous tests in excel – import is a standard JIRA functionality

  • The easiest way to distribute tests to testers is to use Test Executions

  • Creating test cases always takes some time – so think about how much detail you will use

  • Show basic usage of X-Ray to all of your testers

Example of X-Ray testing board

Â