Guidelines, hints/tips for test design at L6
| Level | Environment cleanliness |
| Objective | To ensure that the application does not mess up the external environment and is not messed up by the external environment. All features of the system works correctly on the stated browsers/platforms. |
| What to test | End-to-end business flows will be considered as EUT at this level |
| Test for what | Typical issues looking for at this level are issues related to environment changes. Issues like improper usage of the shared resources (disk space, memory, cpu, Os resource), not considering the varying conditions of the running environment, compatibility issues with various combinations of environment etc will be targeted at this level. |
| Design guidelines | Since the objective is to validate for the handling of issues due to varying environment conditions, it is mandatory to know about the environment and the factors that can mess up the environment, those factors in the environment that can affect the behavior of the application, various combinations of environment where the application is supposed to run etc. |
| Hints/Tips | List down the factors from the environment that can affect the behavior of the application, understand how those factors will be varying and the corresponding impact on the application, various platforms the application is supported, browsers and other devices that the application need to be compatible with etc. Then identify what features need to be validated against each of these environment changes and ensure application is able to handle any changes from the environment gracefully. |