About Requirement
In Appsvio Test Management (ATM), a requirement is any Jira work item, for example an Epic, a Story, or a Task. Most often, teams use Epics and Stories that already exist in Jira.
A requirement is connected to a Test Case with a standard Jira link. A requirement can have no Test Cases, one Test Case, or many Test Cases.
Why define requirements
Defining requirements in ATM is optional. You can write and run tests without them.
If you don’t define what a requirement is, you can’t use the Coverage and Traceability reports. The Coverage report shows which requirements have Test Cases. The Traceability report shows the Test Cases of each requirement, their executions, and their defects. See Coverage Report and Traceability Report.
Set up requirements in a Testing Project
In your Testing Project, you choose the spaces and work types that hold requirements. Mapping requirements is optional. You can choose several spaces and work types. One space and work type pair can be the default, which the Jira Create screen suggests automatically.
When you map requirements, you must also choose the Jira link type that connects them to Test Cases. We recommend the “tests” / “is tested by” link type, which the sample project uses. The Testing Project wizard has no default link type.
Several Testing Projects can share the same requirements. See Testing Elements.
Requirements kept outside Jira
Many companies keep requirements outside Jira, for example in Excel. In that case, consider one of two options:
- Move all the requirements to Jira.
- Create placeholder work items in Jira for them.
In both cases, link the requirements to your Test Cases.
Requirements and Test Cases in ATM
On a requirement, the Test Management panel shows the linked Test Cases and the coverage. From there, you can create a new Test Case or link an existing one.
You can also link requirements from a Test Case, or link many Test Cases at once with Link requirements in the Test Repository. See Coverage with Test Case.