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.
1. Requirement list
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.
2. Create A new Requirement
To create a new requirement
Click on Create requirement button on top right section → Task
Fill in Requirement name and description
3. Edit and Delete a requirement
3.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.
3.2 Edit a requirement
In the requirement list section, click on a requirement name to open to requirement details dialog
In the requirement details, update its status and assignee as needed
4. Manage Test cases of a Requirement
4.1 Associate Test Cases
In order to add/associate test cases to a specific requirement
Click on a Requirement Title link in the Requirement list
In the requirement details dialog, choose Test cases tab
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.2 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. Analysis and Scope Calculation
Agile Test makes it easy to analyze the state of the Requirements.
The coverage status can be calculated for different analysis scopes. Once the analysis scope is changed, the status is automatically recalculated for the new scope
The status of the requirements is calculated as the following:
Uncovered status: if there is no test -> the requirement will be considered UNCOVERED
Covered status: if the test script is added, but there is no test run, then the requirement will be considered as COVERED
Not Run status: if the test script and test case are added, but there is no test run, then the requirement will be considered as NOT RUN
SKIP status will not affect the requirement's status
Unknown status: If there is any query , retest, or blocked test AND no fail tests, no to do test, the requirement will be considered as UNKNOWN
OK status: If all tests are passed or skipped, the requirement will be considered as OK
NOK status: If there is any failed test, the requirement will be considered as NOK
Not Run status: If there is any to do test and no failed test, the requirement will be considered as NOT RUN