This presentation is prepared for the customer to show basic info about X-Ray and possible usage on the project. I checked with our IT and the X-Ray module can be used by the customer if they use our Jira on the project - in that case, there are no special fees for the customer. Part of the presentation should be also live demo of the X-Ray - be sure you know how to show what is mentioned in slide 5. The presentation can be shared with the customer.
...
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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
| Info |
|---|
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:
Test PlanThe demos includes:Jira Legacy
| server | System JIRA |
|---|---|
| serverId | 0e65890b-f559-36c3-b4f7-807e5b0df1a0 |
| key | PFTQA-209 |
Test Executions:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Testing Board: (See folder “UAT demo test cases”)
Excel with UAT test cases is on Sharepoint: https://pricefx.sharepoint.com/sites/PFX/Customer%20Solution/Forms/AllItems.aspx?id=%2Fsites%2FPFX%2FCustomer%20Solution%2F30%20Customer%20Solutions%2FCompetencies%2FQA%2FTemplates&viewid=60a4c9d9%2D575b%2D4ee2%2D8a7e%2D09776e8f55b8
...
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:
...
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:
| Info |
|---|
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 inDownloads.
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
...