Requirements

A requirement refers to a specific statement or condition that defines what a product, system, or service must achieve or possess to meet the needs of stakeholders. Requirements serve as guidelines and constraints that shape the design, development, and implementation of the project.

To manage requirements of a specific project, go to Test Management (left hand menu)→ Requirements.

Initially, users can find the requirements displayed on the right hand section.

On the left side, you will find a dedicated section where you can create, edit, delete, and organize all the requirement groups in a hierarchical view.

1. Create new Requirement

To create a new requirement

1. Click on Create requirement button on top right section → Task

2. Fill in Requirement name and description

   

    

2. Edit and Delete a requirement

2.1 Delete a folder

Find delete button in Action column to delete your desired folder.

Note: Only admins can delete a requirement by going back to Jira issues.

 2.2 Edit a requirement

1. In the requirement list section, click on a requirement name to open to requirement details dialog

2. In the requirement details, update its status and assignee as needed

   

3. Link Test Case to Requirement

In order to add/associate test cases to a specific requirement

1. Click on a Requirement Title link in the Requirement list

   

    

2. In the requirement details dialog, choose Test cases tab

3. Click on Add test cases button, and select either New test case or Existing test cases

   

    

   • If you chose New test case, a Create issue dialog shown up, fill in all the necessary and click on Create button

     

      

   • If you chose Existing test cases, you can select test cases by searching by name, filter by fields and conditions, or using JQL. Then click on Add Selected button

     

      

4. Remove Test Cases from an associated Requirement

In order to conduct bulk delete, select multiple test cases and click on Remove button from items selected

5. Requirement Status

A Requirement run status is calculated based on its link with Test Cases and Test Scripts. In other words, only Test Cases and Test Scripts run status (depicted as 1) affect the run status of the Requirements (depicted as 2).

Below are the scenarios of how the Requirement run status is calculated (the effect of Test Sessions on Requirement run status)

*N/A: Not Available

The Requirement run status will be calculated as COVERED if users choose to use only Test Session feature (exploratory tests) based on a requirement.

6. Test Coverage and Scope

For other Requirement run status, please refer to this page: