Requirements are a vital part of the test management paradigm, as they allow you to track whether your product is, in fact, what's expected of it, and keep your testing efforts in accordance with the requirements documented earlier.
In Qase you can manage product Requirements, too - the section "Requirements" is dedicated to that:
To create a new Requirement, hit the "+Requirement" button in the Requirements section:
A Requirement has several parameters:
- Description: optional, add any extra information about your requirement here.
- Parent: here you can define whether a requirement should be a sub-requirement of another higher-level requirement. If there are no requirements created yet, the only option available will be "Root".
- Status: you can choose from several Requirement statuses - Valid, Draft, Review, Rework, Finish, Implemented, Not Testable, Obsolete.
- Type: a requirement can be either an Epic, a User Story, or a Feature.
- Attachments can be provided for additional context of a requirement.
- Next, attach the Test Cases that will be covering your requirement:
Once a requirement has been created, you can see its details in the section, create a "child" (or a sub-requirement), edit or delete it, and navigate to test cases that cover this requirement by clicking TC title:
Requirements section also allows you to look up items by title or description using the search box, or filter out specific requirements by a certain parameter (Author, Status, Type, or Creation Date):