Guidelines, hints/tips for test design at L7
| Level | Attributes met |
| Objective | To ensure that the system meets the stated quality attributes (Performance, Volume, Load handling capacity, security. |
| 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 non-functional requirements. Issues like performance issue, load handling issue, concurrency usage issue, resource consumption issues at peak load, security issue, endurance issue etc will be targeted at this level. |
| Design guidelines | Since the objective is to validate the end-user expectation, it is mandatory to know about the various types of users, their usage pattern, peak/typical number of users in each user type, what are their expectations, who is using what features of the system, what is the typical/peak number of transactions supported per unit time etc. |
| Hints/Tips | Identify the metrics to be measured based on the expectation of the users. Once we understand the above mentioned details, construct a table that maps the user type, and operations. Then for each user type map distribute the set of users varying form typical/peak number and combine the load pattern based on the typical usage pattern in a real time situation. Create scenarios to simulate the real time usage of the system and measure the identified metrics behavior in normal condition, peak condition and worst condition. |