Guidelines, hints/tips for test design at L5
| Level | Flow correctness |
| Objective | To ensure that the individually tested features are integrated smoothly and work as intended as part of a flow/use case. |
| What to test | EUT at this level can be a requirement/ use case/usage flows. Combination of features as business requirement flow will be considered as EUT here. |
| Test for what | Typical issues looking for at this level are issues related to the end-to-end flow business logic implementation. Issues like not handling the pre-conditions of interaction, wrong interaction sequence, combined business logic behavior etc will be targeted at this level. |
| Design guidelines | Since the objective is to validate for the correctness of interaction behavior of entities, it is mandatory to identify and understand the dependent entities and how the depend each other. What are the pre-conditions to be satisfied for the interaction, what are the expected out puts from the interaction etc. |
| Hints/Tips | Use requirement-feature mapping to identify the features involved in each flow/requirement and then use a diagrammatic representation (flow-chart) of the usage flow to identify the main and alternate possible flows of interaction among the features and the expected outputs. Construct scenarios to ensure each flow is working as intended. |