Do you know why to design test cases after learning so long about use case design

Even if the test is familiar , Once the product is developed , Get the test and start to use it to find bug Do you , I think even if the test is familiar with the product , In the process of testing, I must have forgotten the function of the product , Even familiar with documents , Because there are too many function modules of a product ; If testing is only based on familiarity with requirements documents , Just start messing up , No plan, no goal, start testing , In the end, I forgot what I had done , Let alone test efficiency , Can do the test well .
　　 So in the stage of product planning and design , Testing has begun to participate in the product , Get familiar with products , Collect various documents and organize them into some operation steps , This forms the test case , Then the life cycle of use cases begins .
　　 The first function of use cases is , Transform product requirements into an operable step , It is convenient to test step by step and plan in the future . And in such a conversion process , Because of this strong logic of operation , Often the test can find the design in the product bug, Because in the process of designing use cases , It's actually simulating the use of products in your mind ; therefore , The process of writing use cases is actually a process of testing production requirements .
　　 The second function of writing use cases is to verify whether the requirements of the product are reasonable . If you find that the product demand is unreasonable , Or there are contradictions in needs , Even unclear places , At this time, our use cases can't go on ; Because the previous step we wrote may have multiple results , What is the result of the product , Or the results .
　　 So we need to find products to confirm ; A look at the product , This really needs optimization , Or need to consider or need to come up with a better plan . Here is the third function of test cases ： Supervise the product to make more detailed design for requirements . And when the product comes up with a good plan , Gave a test reply , So the test writes it into the test document .
　　 This reflects the fourth function of test cases ： Record the design details of the product , Ensure future access . The test has such a process of communicating with the product , I have a deeper impression of this module . Here is the fifth function of test cases ： Deepen testers' understanding and impression of the product .
　　 When the product is developed , The preparation for the test is almost done , So testers began to test according to the description of test cases , Mark the completion of each use case ; In this way, the test also knows what operations they have done , Avoid random testing without purpose , And pass the execution number of test cases , Get a general understanding of the test progress of the module , This reflects the sixth function of test cases ： Reaction test progress . In the process of executing use cases, testers often suddenly find that the steps of the originally designed use cases , You can also do such an operation , So I found out bug, This reflects the seventh function of test cases ： Help discover and expand the scope of testing , Expand test coverage , Discover hidden defects in software .
　　 Well, by this time , Test cases have grown into a young age . In the process of software testing , We perform as described in the test case , It can roughly determine the progress of the test . During the test , We will find that bug, And this bug Maybe there is no step description in the test case , But considering that he may reappear in a later version , So we sorted out its steps , Form a new use case , To test whether it will appear in later versions , Here is another function of test cases ： Facilitate regression testing , Reexamine bug Whether there will be .
　　 After the software version goes online , Due to various user habits , And various usage scenarios , And various terminal environments , There will be some things that are not found during the test bug, Something like this bug The impact on the product is relatively small , But it is also the optimization point of the product . After the first release , Due to user feedback , And the statistics of the product on the user's operation behavior , The product has a better scheme , Or the product should try something new , So the demand begins to change . Changes in requirements lead to partial failure of test cases , So the test needs to update the test case , Delete invalid use cases .
　　 This reflects a flaw in test cases ： Increased test maintenance costs . Sometimes, due to the tight time of product launch , Writing examples will take a lot of time , In contrast, the time for testing is less , This has another defect that reflects the test case ： It costs time . Often in such circumstances , In order to avoid insufficient testing time , We will spend a very short time listing important test points to start testing . In order to avoid missing test , We will refer to the test cases of previous relevant modules . This reflects another advantage of test cases ： Provide reference information for testing in emergency .
　　 Well, here , continue . There will always be personnel changes in the process of product testing . Most newcomers are not familiar with the product , Let them test according to the previous requirements , It must be missed . Because the product has experienced demand changes in the process of launching , And also found many potential problems , Newcomers certainly can't see these from product requirements and products . So they need test cases to help test , Understand the potential problems that have occurred before , More familiar with the product and its testing ; Here is another test case ： Training new people , Save coaching time for newcomers . Why does it save time for new people to coach , Because new people often don't understand a lot when they see products , So they often ask “ Predecessors ”, And if the seniors arrange them to execute well maintained test cases , Then many problems are solved in the process of executing test cases , So the number of questions asked will be reduced , It saves time for their guidance .
　　 And let's take a look at the current mobile outsourcing test .
　　 We know that some functions of mobile phones will not change for many years , Especially the same series of mobile phones . Like text messages 、 conversation 、 bluetooth 、 Mobile Notepad 、 The radio 、 Recorder and so on . And the people who test the functions of these mobile phones are not fixed , Because of the mobility of people , Once the personnel flow away , Then few people are familiar with the testing of these functions ; What problems will happen to him , Which behaviors are redundant functions , Which functions are incorrect? These require familiar people to perform the test . The company is smart , In the long-term operation, he knew that such things would happen , So they put their mobile phones where they are prone to problems , Or have problems before , Or some information designed at the beginning is sorted into operable documents , recorded , This forms the test cases we see . Then the new employee will have the basis for the test , They are often assigned to some test cases to execute , On the one hand, the reason is that the tested products are consistent with the description of the document , On the other hand, let the new employees be familiar with the products , And the general steps of product testing .
　　 So the purpose of test cases is for newcomers , It improves the testing efficiency of newcomers , And play the role of training new people .
　　 If a product stops maintenance , Then all test cases will fail , The life cycle of this test case ends . And a new product , A new life cycle has begun . therefore , Test cases accompany the whole product life cycle .
　　 The article says here , Let's summarize the advantages and disadvantages of test cases ：
　　 advantage ：
　　1、 Transform product requirements into an operable step , It is convenient to test step by step and plan in the future .
　　2、 Verify whether the requirements of the product are reasonable
　　3、 Supervise the product to make more detailed design for requirements
　　4、 Record the design details of the product , Ensure future access
　　5、 Deepen testers' understanding and impression of the product
　　6、 Reaction test progress
　　7、 Help discover and expand the scope of testing , Expand test coverage , Discover hidden defects in software
　　8、 Facilitate regression testing , Reexamine bug Whether there will be
　　9、 Provide reference information for testing in emergency
　　10、 Training new people , Improve the testing efficiency of newcomers , Save coaching time for newcomers
　　 shortcoming ：
　　1、 Increased test maintenance costs
　　2、 It costs time

Article reprint link ：http://www.51testing.com/html/24/n-4477624.html