If the business scenarios are not identified well, the tests will not conform to what will happen during production, and will therefore be useless, or even dangerous, giving the false impression that the targeted platform handles the load without problems.
It is therefore critical to identify the relevant business scenarios and weight them.
To define these scenarios, we can:
- Retrieve the statistics of the application if they exist (for example, the daily or monthly number of business transactions, an analysis of web statistics (access log, analytics tools...), and so on)
- Define them with Users/Business User/Product Owner
For the number of scenarios, it is advisable to apply the Pareto Principle (https://en.wikipedia.org/wiki/Pareto_principle), also called the 80/20 rule, and therefore to take (at least as a first step) only the 20% of scenarios that cover 80% of the scope of the application – for example, by not simulating different...