Decide your project organization strategy

Select the best approach to match your QA strategy with Jira project configuration. 



AdvantagesDisadvantages

All-in-one project

Requirements, Defects & Tests in the same Jira project

(tick) Info all together and visible to the whole team

(tick) Same context - testers & dev

(tick) Less administration effort

(tick) Simple to understand

(error) Extra info that may be confusing to the team


Separated projects

Separate Tests from Requirements and Defects

(tick)  Dedicated project for Testers

(tick) Less information inside the project 

(tick)  Permissions can be more granular 

(error) Extra administration effort

(error)  May promote team divide


If you want to go for the easiest and simplest approach go for - the all-in-one project. 



Share your strategy with your Jira Admin

Once you know how you will organize your project, share your choice with your Jira admin and ask them to perform the needed actions for setup: 

  • Enable Xray for existing projects or
  • Create new projects

Select your Planning Strategy 

When designing your planning strategy you will decide which tests you want to perform, and who and when will execute the tests. Also, you may want to prioritize some of the tests and focus on specific requirements.

Your planning strategy must reflect your methodology, here are some options: 


(tick) SCRUM based approach - Create one Test Plan per Sprint


(tick) Feature Approach - Create one Test Plan for the features (maybe epics in Jira) you are able to address at your WIP. More suitable to Kanban. 


(tick) Release Approach - Create one Test Plan per release (Fix version in Jira) or interim release/milestone. More suitable to waterfall methodology.


(tick) Test Categories Approach  -  Create one Test Plan per category of tests, for example, Regression Tests, Security Tests, Non-functional tests.


Check the next step to see how to Create a Test Plan. 

Create Test Plan

Now that you have decided your test planning strategy you can create your first Test Plan.


  1. Click "Create button" and Test Plan issue. 


2. Besides Summary, you may want to fill out Fix Version to indicate that you're tracking the results of the Tests for a specific version. This only makes sense if you are working with versions. 




3. At Test Plan Details you can add Tests at "Tests associated with a Test Plan" or you can do it later at the add button.

Info

In order to add Tests to your Test Plan, you need to have them created beforehand. Learn more about creating Tests in the Tester Onboarding Course.

Explore possibilities to organize your Tests

You can organize tests using two different approaches: 

  • Test Repository - is a project page which enables the hierarchical organization of Tests at the project level by allowing you to organize Tests in folders and sub-folders. You can also perform several actions from this page including, creating new Tests, creating new Test Plans, Test Sets, Test Executions for a group of Tests, etc. This is the recommended approach whenever you have a large number of Tests and want to manage them more effectively.


  • Test Set - is an issue type for organizing tests, and it is a flat list of Tests and is a simple way to create different groups of Tests. You can easily select them when creating Tests Plans or Test Executions.


Select your favorite reports

Xray provides several ways to make it easier for the entire team to have a clear view of the overall readiness of the project.

As part of your daily tasks, use the dedicated reports and gadgets available in your customized dashboard to evaluate your testing progress.

The most popular reports are: 

ReportWhat do you get
Overall Requirement Coverage Report

Provides the coverage status of requirements for some given context (i.e. Version/Test Plan).

  • Analysis can be done by “Version” or by “Test Plan” and on a given Test Environment
  • Takes into account results performed on that scope
  • Groups requirements by component, priority, etc
Traceability Report

Shows the requirement traceability, from requirements to defects.

This helps you analyze the requirements and related Tests, Test Runs and defects, so you can quickly identify uncovered or incomplete/faulty requirements.

Test Plans Report

Shows a list of Test Plans with consolidated information for each one, such as test statuses count, overall progress and Test Environments metrics.

Test Executions Report 

Shows a list of Test Executions with some metrics related with each execution, such as the tests count per run status, per test type, overall progress and linked defects

Historical Requirement Coverage

Shows the evolution of the requirements coverage status for the given period.

The number of requirements may be analyzed by percentage or absolute values.

If you want to analyze the current status of your release, you might find it useful to check the Overall Requirements Coverage Report and the Traceability Report. You might also use these reports to perform an analysis by Test Plan, in that case it only takes into account results performed on that scope of the test plan.



  1. Go to Xray Reports and select the report you want to see. 


       




Explore and learn more by taking the QA Manager onboarding course.




  • No labels