Guidelines, hints/tips for test design at L4
| Level | Behavior correctness |
| Objective | To ensure that the functional behavior (completeness/correctness) of the EUT is implemented as indented. |
| What to test | EUT at this level can be a feature, user story, any component that has an independent functionality. |
| Test for what | Typical issues looking for at this level are issues related to the business logic implementation of the EUT. Issues like not considering condition(s) that govern the behavior of the EUT, misuse of conditions, wrong order of combining the conditions, missing possible value of a condition to consider etc will be targeted at this level. |
| Design guidelines | Since the objective is to validate for the correct implementation of the functional behavior of the EUT, it is mandatory to identify and understand the conditions that govern the functional behavior of the EUT, the possible values that each conditions can take, and identifying the expected outputs from the EUT. |
| Hints/Tips | Use Descriptive-prescriptive approach to identify the conditions that govern the behavior of the EUT, use behavior modeling to model the behavior and use techniques like Decision table to combine the conditions optimally and derive scenarios out of it. |