Detailed explanation of scenario method for common test case design methods

Scenario based use case design

Today's software is almost always triggered by events to control the process , When the event is triggered, the scene is formed , Different triggering sequence and processing result of the same event form event flow .

This idea in software design can also be introduced into software testing , Vividly depict the situation when the event is triggered , It is helpful for the test designer to design test cases , At the same time, test cases are easier to understand and execute .

The use case scenario is used to describe the path through the use case , From the beginning to the end of the use case, traverse all the basic and alternative flows on this path .

The scene that

Basic flow ： Is the most important path through the use case , The black line in the picture .

Alternative streams ： Start with basic flow , Then it will be executed under certain conditions .

• It is possible to rejoin the basic flow （ Alternative streams 1 and 3）

• May originate from another alternative stream （ Alternative streams 2）

• Terminate the use case without rejoining a flow （ Alternative streams 2 and 4）

Basic design steps of process analysis method

• Draw a business flow chart

• Define state nodes and condition branches

• Determine test path

• Select test data , Construct test cases

Summary of scenario method

The focus of the scenario approach is on testing the process , Therefore, each process can be verified with a set of test cases .

The scenario approach needs to be carried out in two steps , The first step is to determine the business process of the system , The second step is to verify each business process with several test data .

Wrong guess

The concept of error guessing ： Based on experience and intuition, we can infer all kinds of possible errors in the program , So as to design test cases with pertinence .

The basic idea of the wrong guess method ： List all the possible errors in the program and the special cases that are prone to errors , Select test cases based on them .

give an example ：

• Many of the common errors in modules that have been listed during unit testing 、 Mistakes found in previous product tests, etc , These are the summaries of experience .

• The input data and output data are 0 The situation of 、 The input form is blank or the input form has only one row . These are all error prone situations , The examples in these cases can be selected as test cases .

• Wrong guessing method for rare words .

limitations

Learning resource sharing

Finally, thank everyone who reads my article carefully , Watching the rise and attention of fans all the way , Reciprocity is always necessary , Although it's not very valuable , If you can use it, you can take it

These materials , For those who want to engage in 【 software test 】 For our friends, it should be the most comprehensive and complete war preparation warehouse , This warehouse also accompanied me through the most difficult journey , I hope it can help you ！ You can get it for free by joining our communication group below , I hope that's helpful …….