Scenario definition
Define the official version: a method to improve the test effect by using scenarios to describe the function points or business processes of the system.
My cliché version: You go from A to B, one of the ways is that you walk beautifully every step of the way from the beginning to the end, and the birds and flowers are fragrant on the road. There are many other ways of walking where you take other paths, but you end up on B, even if you fall in the middle, go around a river, etc. These are scenarios.
event stream
Elementary flow: 1. There is only one elementary flow
2. The simplest path through the use case, referring to what happens when each step works "normally"
Alternative flow: 1. There can be multiple
2. Optional or Alternate case, abnormal event flow.
A scenario is an instance of an event flow, consisting of steps of a basic flow or (basic flow + alternative flow), indicating that the user performs a sequence of system operations.
The more candidate streams, the more scenarios, and the more execution paths, which will lead to scenario explosion ---> Select typical scenarios for testing, which are basically as follows:
1. The minimum number of scenarios is equal to the total number of basic streams and alternative streams.
2. There is one and only one scene that contains only elementary streams.
3. Corresponding to an alternative stream, there should be at least one scenario covering the alternative stream, and in this scenario, covering other alternative streams should be avoided as much as possible.
Scenario design steps
1. Analyze the business under test and find out the basic flow and alternative flow
2. Generate different scenarios according to each basic flow and each alternative flow
3. Generate corresponding test cases for each scenario
4. For all the generated tests Re-examine use cases, remove redundant test cases, determine test data values for each test case after confirming test cases
Example--ATM scene
The basic flow is the flow direction in the box.