This section will provide a quick overview on X-Ray and the benefits it can offer you.
LEARN MORE: Check out more information on X-Ray here.
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 in 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
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 - Story, Change Request, Improvement, Epic, Sub-Task, press Save button
Defect Mapping - Bug, press Save button
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
X-Ray demo recording on Sharepoint: - note the recording is just for internal purpose
Video recorded by Jaroslav Skála on Avery Dennison EMEA project: