Versions Compared

Old Version 5

changes.mady.by.user Ioana Kocurova

Saved on

compared with

New Version 6

changes.mady.by.user Mike Deskis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We started to use X-Ray in 04/2021, it was already used on many projects for many customers and since then it became mandatory tool for our projects. On some projects, the customer decided to use it even for UAT phase.

Benefits of X-Ray on the project

  • Test cases and test results are easily visible to our team and to the customer

  • Tool can be used for our Feature Sprint testing and also by the customer for UAT testing

  • Tool is standard part of configuration for every new Jira project, it just needs a simple configuration to be used

  • Test documentation is correctly linked to correct user stories so it is clear what was tested because of which user story and with which result

  • Easy knowledge sharing when replacement of QA Analyst is needed on the project

  • Customer can use our test cases as the starting point for their UAT test cases

  • Monitoring of testing progress helps a lot to PM to be sure about project status

  • Test cases are easily visible as Test issue types, Comments are not used for test cases any more. It will help to have Comments section smaller

...

(info) Note: Using X-Ray on new projects is mandatory for QA Analysts (unless there is a very special reason for using another tool), but it is just highly recommended for customers to use it for UAT phase

X-Ray

What is X-Ray?

  • Test Management tool in Jira. Needs configuration at the beginning, can be used by the customer. Can be safely configured also on ongoing projects.

  • Note that X-Ray is used by Pricefx on projects, Partners can use different test management tool, so they can take the following text as recommendation what they should do with their own system

Why to use X-Ray on the project

  • evidence of QA work - test cases and test results

  • all project documentation stays in JIRA

  • easier communication with project team and customer as all QA documentation is easily visible

  • visible progress of testing - it is clear what was already tested and which tests are in progress and what will be tested as next tests. All test cases are properly linked to correct user stories so also test coverage is visible.

  • customer can use it for UAT phase to create UAT test cases, organize UAT testing and monitor the progress

  • auditors can ask what was tested on the project and where is the documentation

  • another project documentation - can be used by support team or when new people are coming to project team together with user stories

  • test cases can be a starting point for starting test automation on the project

 

Configuration by QA

→ note that Admin rights are necessary for this configuration - if you don’t have them, ask your PM or QA Competence Leader

  • Project Setings → Apps → Xray Settings

  • Test Coverage - Move “Story”, “Change Request”, “Improvement”, “Epic”, “Sub-Task” from left column to the right column and press Save button

  • Defect Mapping - Move “Bug” from left column to the right column and press Save button

  • Now X-Ray is properly configured and you can use it on the project

Tips for using X-Ray on the project

Administration on the project

  • Create Test Plan for the whole project

  • Create Test Execution for every Feature Sprint (can be just for the first Sprint at the beginning)

  • Create first structure in Testing Board - structure for Sprints

Create test cases on the project

  • Create new Test from user story you need to test - several test cases can be created - creating from user story ensures Test is correctly linked to propper user story

  • Add Tests to Testing Board to folder named after user story

  • Add Tests to Test Plan for the project

  • Add Tests to Test Execution for the correct Feature Sprint

  • Modify Description of Tests to describe what you need to test.

✅ Don’t use Test Steps - it is very time consuming for later administration and it is not a good approach for Imports/Exports of test cases - test details should be described just in Description field

Testing and reporting results

  • Note: Test Execution must be correctly linked to Test

  • Open Test on a new Tab

  • Display Test Runs

  • Click on icon to execute Test

  • Report test results to Findings part (details about testing to Comments and screens to Evidence)

Overview of test results (mostly for PM)

  • Open Test Plan for the project

  • Choose Test or Test Execution tab to se overview of results for all tests or just for specific Test Execution

...