Releases and requirements

Plan releases, write the requirements your automations must meet, and link them to the test cases that verify them.

Releases are the versions or milestones you test for. Requirements describe what an automation must do. A requirement can be planned for a release, and test cases verify it; Coverage shows which requirements are verified. Create a release# Open Planning ▸ Releases and select New release. Enter a Name and, optionally, a Version, Description, Start and End dates, Status (Planned, Active, Testing, Completed, Cancelled, Archived), Owner and Labels. Select Create release. The list shows each release's dates, status, number of requirements and owner. Filter it by status with All statuses. Open a release to see its Requirements, its requirement Coverage and Automation coverage, and its owner. Change it with Edit. Create a requirement# Open Planning ▸ Requirements and select New requirement. Enter a Title and a Description. Choose the Type (from the project's requirement types), Priority (Low, Medium, High, Critical) and Status (Draft, In review, Approved, Implemented, Verified, Deprecated). Optionally set the Owner, the Release it is planned for, a Parent requirement, an External reference and External link to the item in your tracker, and Labels. Select Create requirement. The list shows each requirement's type, release, external reference, labels, priority, status, how many test cases verify it (Not covered when none) and owner. Select several rows to change them together. Use ⋮ on a requirement to clone, archive or delete it. Link test cases to a requirement# Open the requirement and select the Test cases tab. Select Link test cases, tick the test cases that verify it and confirm. Select Unlink to remove a link; the test case stays. You can also link from the other side, on a test case's Requirements tab. Next steps# Test cases Coverage

Create a release

Create a requirement

Link test cases to a requirement

Next steps