Requirements Management with Coverage

Requirements management in BesTest gives your team a live view of which requirements are tested well enough and which still need work. Open a requirement and the stats bar across the top answers the first questions at a glance: how significant it is, whether it is Covered, Partly covered or Not covered, how its test cases performed recently, which Jira work items it connects to, and whether it has been approved.

Coverage is not "linked or not". Each requirement gets a significance from its impact and its complexity, and that significance sets how many linked test cases it needs: 8 for Critical, 5 for High, 3 for Medium, 1 for Low. The Coverage card shows the count in plain words - "Test cases: 3 linked of 5 needed" - so a critical payment requirement never looks covered just because one smoke test is linked to it. When you know better than the formula, set the Decision to Covered or Not covered; a hand icon marks it as a person's call, and you can switch back to Automatic at any time.

Linking happens where you read: the Traceability card on the Overview lists the connected work items and test cases, with Create & Link and Add Existing buttons, and the Links tab shows every connection (work items, other requirements, test cases and cycles). In the catalog, the Coverage and Test Results columns plus the Coverage filter list the gaps before release.

Requirements are first-class BesTest records, not Jira issues, so they never bloat your backlog. They can go through the same review and approval workflow as test cases, so business and functional needs are signed off before anyone writes tests against them. And when a story lands with ten acceptance criteria, Create in bulk turns ten lines into ten requirements - from the requirement catalog or from the Jira work item panel, already linked to the work item.