Requirement Coverage Overview

Like in ALM, you can create coverage between requirements and business process tests. The difference is that when working with business process testing, instead of covering each requirement only at the level of a test and its configuration(s), you can define coverage by criteria, such as flows or business components. This enables you to determine if a test passed or failed on a more granular level. For example, a test can be considered passed even if just one of its business components passed, such as the most critical one. Less critical business components have no effect on the overall status of the test.

The logic used for calculating coverage by criteria is similar to the logic used for calculating coverage by tests and test configurations. For conceptual details on coverage analysis for tests and test configurations, see the Micro Focus Application Lifecycle Management User Guide: Requirement and Test Coverage Overview.

For task details, see How to Create Coverage by Criteria.