Equivalence class, boundary value, application method and application scenario of scenario method

Equivalence class ：

         In many cases , The test method that many people think of is exhaustive testing , Exhaustive testing is the most comprehensive test , But it's not realistic when there's a lot of data , The test efficiency is too low , Later, in order to reduce the workload of testers, improve the efficiency of testing and achieve the best test quality , Gradually, there are test methods for equivalence classes . As long as there is an input box to input data, you can use equivalent classes for testing , Select representative data from a large number of data for testing .

Usage and applicable scenarios of equivalent classes in testing ：

        1） Divide equivalence class One , It should be according to the input conditions （ Such as the range of input values , The number of values , The type of value , What are the input conditions ）, Divide valid input and invalid input （ Effective equivalence class and invalid equivalence class ）   , in general , What is within the requirement is a valid input , All other than requirements are invalid inputs .  

                 for example ： Input submit one 11 The number of digits     

                            Can be divided into a valid equivalence class ： Submit a correct 11 The number of digits     

                            Multiple invalid equivalence classes can be divided ：

                                                                         To submit a 10 Number of digits or 12 Number of digits           

                                                                         The content submitted is not digital                     

                                                                         Submit empty data                     

                                                                         Does not conform to the number format ..  

            2） Design test cases      

                          One , Make a test case cover as many valid equivalence classes as possible , Until all valid inputs （ Yes                                           effect Equivalence class ） Be covered   .       

                          Two , A use case can only cover one invalid equivalence class , Until all invalid inputs （ Invalid equivalence class ） By                                       cover Finished .

The boundary value :

          Long term testing experience tells us that , A lot of errors occur at the boundary of the input or output range , Not inside the I / O range . Therefore, test cases are designed for various boundary conditions , We can find out more mistakes difference ： Although the boundary value analysis method is a supplement to the equivalence class , But it is different from equivalence classes , Boundary value analysis is not to select any one of the equivalence classes as a representative , Instead, make each boundary of the equivalence class as a test condition .

Usage and applicable scenarios of boundary values in testing ：

The boundary value analysis method is applicable to all test points related to numbers .

         Columns such as ： One , An input box restricts the input of 2-9 Characters ,    

                           The boundary value to be tested is ：1 Characters ,2 Characters ,3 Characters ,8 Characters ,9 Characters ,10                                Characters

                      Two , Program night 20 Automatically publish new content at o'clock ,

                            The boundary value to be tested is ：19 spot 59 branch 59 Second unpublished content 20 Press the release content

                      3、 ... and , Each time you send a red envelope, you can only send 1-100 Yuan's red envelope      

                             The boundary value to be tested is ： Hair 0.99 Yuan a red envelope , Hair 1 Yuan a red envelope , Hair 1.01 Yuan a red envelope , Hair 99.99 element                                 Red envelopes , Hair 100 Yuan a red envelope , Hair 100.01 Yuan a red envelope   ...

Applicable scenarios such as , Size , location , Speed , Coordinates and so on ,..

Scenario analysis ：

         Analyze the scenario of software application , From the perspective of users , Design test cases from the perspective of scenarios , Is a user oriented test case design method . Care about what users do , It's not about what the product does , The test point is not on a single function, but on the whole business process , in general , Is to use the product from the perspective of users .

Usage and applicable scenarios of boundary values in testing ：

         Case study ： Commodity payment purchase

                 Analyze basic flow ： After the user selects the product , payment , Input password to pay successfully

                 Analyze alternative flows ：1） Password error during payment , Re - enter to re - pay for the purchase         

                                      2） Not logged in during payment , Go to login to re pay for the purchase          ...

                  Abnormal flow :  1)   During the payment process, the goods are off the shelf or there is no inventory, which makes it impossible to purchase   

                                2） Insufficient balance at the time of payment makes it impossible to purchase   

                                3） During the payment process, the number of password input errors is too many, resulting in account freezing and unable to purchase     

                                 4） The price of the goods is changed during the payment process, which makes it impossible to buy ..     

                        Generally speaking, the abnormal flow is that the business is not completed due to some errors or abnormal operations .

Welcome to thumb up + Collection