Requirements

Requirements represent business or functional needs that must be validated through testing. They can be organized in folders and linked to test cases to establish traceability. When all linked test cases exist, a requirement is considered "covered," enabling coverage reporting and gap analysis.

Overview

The Overview tab stands from different cards:

• Top bar shows Requirement's calculated Significance and Test Coverage
• Main card contains the main data
• Linked Items shows what Work Items or Test Cases are connected
• Details shows main attributes
• Significance Assessment area helps autocalculating the significance
  • Dev Complexity x Impact = Significance
  • Expected TCs calculated from this

Review & approval

Requirements use the same review and approval workflow as Test Cases. A requirement can be sent to one or more reviewers and approved before test cases are written against it, so business and functional needs are signed off first.

A requirement moves through the familiar Draft -> In Review -> Active states (with Changes Needed when a reviewer asks for edits). When requesting review you can add a note and a due date; only assigned reviewers can approve or request changes; and every round is grouped into Review Cycles. See Review & approval on the Test Cases page for the full walkthrough.

Links

Items can be linked with

• Work Items
• Other Requirements
• Test cases
• Test Cycles

Coverage in catalog

Connected test coverage and their latest execution is visible in the Test Results column. See which Requirements need coverage, and which performs bad recently.