Back to QMetry All Products Help Page
Requirements Module
- 1 Introduction
- 2 Requirements Module UI
- 3 Managing Requirement Folders
- 4 Requirement Detail Page UI
- 5 Managing Requirements
- 6 Bulk Operations on Requirements
- 7 Linking Test Cases to Requirements
- 8 Sync Latest Requirement Version with Test Cases
- 9 Linking Issues to Requirements
- 10 How to Unlink Issues Linked to a Requirement?
- 11 Associate Releases & Cycles
- 12 Issue Traceability in Requirement
- 13 Requirement Version
- 14 Change Log
- 15 Import Requirements
- 16 Export Requirements
- 17 BDD Editor
- 18 More Features
Introduction
The Requirement module serves as a central repository for storing test requirements and business specifications. You can create requirements manually or import them via Excel using the Import Wizard or import directly from Jira.
Once requirements are imported, both existing and newly created test cases can be linked to them.
Permissions for the Requirements module (View, Modify, Create, Delete, Import, Export, Link, Copy, Versioning) are set under Customization > Roles for individual roles. Ensure that you have the relevant permissions to perform these operations.
Key Features of the Requirements Module:
Add requirements from external development and product management tools. Requirements can be created directly from Jira and kept in sync with Jira.
Cover requirements by linking them to existing test cases that are part of manual or automated test suites.
Perform quick ad hoc executions of test cases associated with a particular requirement. This can help you do quick tests based on pure requirements that might not be covered in a defined test suite.
Requirement reports are also available to analyze the application against varied measures.
Requirements Module UI
The Requirement module offers various customization options to help users create a tailored view of their requirements. Below are the key features of the Requirement Module:
Create New Folder
You can organize requirements into folders and subfolders for improved control and management.
Sorting and Clear Sorting
You can sort the folder structure either alphabetically or by date (newest first or oldest first).
Sorting
Clear Sorting
Include/Exclude Test Cases from Sub Folders at Parent Folder
You can include or exclude requirements from sub folders at parent folder level. By default, Include Entities from Sub-folder remains selected, and entities from sub-folders are displayed at parent folder level on the module list view.
To hide the entities from sub-folder, open the Options drop-down on the test asset tree at left, and select deselect Include Entities from Sub-Folder.
Perform Bulk Operations on Folders
You can perform bulk operations for archiving, unarchiving, copying, and moving folders.
Create New Requirements
You can create requirements directly from the Requirement module UI by clicking on the New button.
Filter Requirements
You can easily filter requirements by any system or custom fields across all module grids. Basic filters like Summary, Release, and Cycle are available by default. For advanced filtering, click the "+" icon and add custom filter fields.
Basic Filters
Advanced Filters
A. Basic: By default, requirements can be filtered by summary, release, and cycle. Enter specific values in these fields to retrieve requirements that meet the criteria.
B. Advanced: You can also apply advanced filters to refine requirements based on fields beyond the basic options.
To apply advanced filters, these are the steps:
Click on the '+' icon (Refer below image).
Select the desired fields for filtering.
Enter the filter values.
Click ‘Save and Apply’.
For example, you want to filter requirements on Priority, and Entity Key. Click on the '+' icon and select the fields on the drop-down list. You can apply an advanced filter on Entity Key to search for test cases using comma-separated entity IDs, without specifying the complete Entity Key, as shown below.
Filtered views are automatically saved for future use, eliminating the need to reapply the same filters repeatedly.
Apply Filter when Jira is Configured with Project
If the QMetry project is synced with at least one Jira project, then only Jira Filters will be enabled for the Requirements module. Two distinct filters: QMetry Filters and Jira Filters will be available to filter requirements.
If you want to apply Jira Filters, first select –
Jira Instance and Jira Project with which the QMetry project is configured and click Apply. If you have only one Jira Instance and Project configured with your current QMetry project, the instance and project will be auto selected.
Once this filter is applied, you can see more filters by clicking on the +