Removing a requirement from a test package.
Removing a requirement from a package will assist in a situation where a test case is associated with a requirement but may not need to be tested under the package. All associated Test Cases will not be included in your test summary report.
To Show your hidden/removed requirements click show hidden requirements at the bottom of the grid.
Hidden requirements will be highlighted and displayed with “REMOVED” status
All cases associated with the requirement will no-longer be reported in your test summary report
To restore hidden/removed requirements.
Blocking a test case associated to a requirement.
You can now block a test case against a particular requirement and package. This will not impact the test case against any other
requirement it is associated to within the package.
- Click on the associated case column besides the requirement and find the case you wish to block.
- Click on the Block case icon. Blocking a case linked to a requirement will only block the case from being tested against the requirement.
- If the case is linked to another requirement it will not be blocked.
Now blocked case Count should increase in your test summary report.
Test Coverage Reporting
Test Coverage is calculated per requirement. If you have a requirement which has 6 test cases associated to it and all cases have been included in the test package then the test coverage for the requirement is based on the test execution status of all cases. The example below shows how our test coverage for a requirement is currently 67%
We then execute test case 1399 against requirement.
Now the test coverage is 83% leaving 1 more test case to be executed to achieve a 100%test coverage.
Executing Multiple Test Cases from a requirement
Execute all test cases against a requirement by simply selecting the Result from the Drop Down.