How to write test cases in software testing technology

1、 Just engaged in software testing , How to quickly master the method of writing test cases ？ How to write test cases ？

Expert analysis ：

1、 Document according to requirements , Completely follow the requirements document framework / Function description , According to my own understanding, it is sorted into use cases . Simply speaking , It is the content described in the requirements document , Edit it again in the format of the use case , Add every conceivable possibility .

2、 Search for similar functional use cases written by other testers , To understand first , Then according to the small difference of the actual needs of the project , Add new / Delete / Change , Form a use case group that meets the requirements .

There is no trick in mastering use cases quickly , Only look at it more. , Many want to , How to write , Review more .

2、 What kind of test case is a good use case ?

If you use a use case to cover a function point, there are great defects in actual operation . First of all, it is impossible to ensure that testers can implement functional use cases in place when conducting integration tests , There may be omissions . Therefore, in the process of test case output , It is suggested that testers use engineering methods to cover process functions with respect to test factors . But this introduces another problem , Customer needs are constantly changing , Requirements in the implementation of design and test case output , There is a great chance of change , This change is bound to have an impact on the original output test cases . The workload of adjustment is sometimes very large , It is possible to push down the whole function and re output the use case . How to solve this situation ？

Expert analysis ： Each use case covers a function point , Is the best ideal state . But the disadvantage of conditional coverage is that each execution will have a long cycle , If some parts cannot be applied to Automation , It will lead to the parallel production of test and development branches that cannot verify each version on time .

There are two ways for reference ：

1. Based on the original test case , Enlarge the fuzziness of use case description again , So that use cases can be used for similar functions with different details . Take the character length of the login interface as 12 Take the double byte user name prompt box as an example ：

Original use case steps ： Enter 11 Chinese characters .

Revised use case steps ： Enter a user name that does not exceed the character length limit in the login interface .

comment ： The original use case steps are only suitable for the login interface. The length of the user name is limited to 11 The above edit box . The modified use case can be used in the user name edit box with any character length . This method can also be used to describe the process , Such as ” Enter the edit user name interface ” Can be replaced by ” Edit user name ”.

2. Establish a relatively complete base use case library , Project use cases exist as a subset of the base use case library . Such a use case library is for a single function , There are many different descriptions and designs . Such as 1 Different fuzzy degrees of points can exist as two different use cases of the same use case . And in the future actual projects , According to the actual needs of the project , Select the appropriate use case group from the basic use case library as the project use case group .

3、 Some companies' black box test cases will evolve into automated use cases . If a single coverage point test case , It will lead to low reuse rate of automatic script code . Questions like this , How to solve ？

Expert analysis ： First of all, it is generally done according to test cases , Single operation , If you want high script reuse , Business function scripts need to be sorted , Call commonly used business functions . This is what your people in charge of designing the framework think . If you think the business utilization is not high , It is written as a public method call .

4、 Is the performance test suitable for boys ？ Some experts say that performance testing and functional testing are not much related , There is no need to learn function testing before performance testing . Is this right ？

Expert analysis ： In fact, performance tests do not tend to boys , Just as there is no male preferred recruitment condition for developers . The reason for this statement , It's just that most boys like logical reasoning better than girls .

Performance testing and functional testing are still related . Some performance tests must also be tested on the basis of certain functional tests .

5、 Tested for several years , I feel no improvement , Always doing some manual tests , When the project comes, test it first instead of writing test cases , When the project is not nervous in the future, add test cases .

Personally, I think this is very irregular . I always think that writing test cases is the most critical , But I haven't written much test cases in recent years . And the examiner will also give you a question during the interview , Let me give you a general idea of how you design test cases . These always make my mind seem empty , No idea . Can experts give some advice .

Expert analysis ：1.“ When the project comes, test it first instead of writing test cases , When the project is not nervous in the future, add test cases ” In fact, this method is not standardized . If you already have a basic test case group , After the project requirements are confirmed , Start the screening of use cases and update the applicable use case groups at the first time , And delivered to each department of the project team for review in the early stage of the project . Such operation is not only for project quality control, but also after the project has problems , Responsibility sharing for testers , Are of great benefit .

2. The design of test cases is one of the most important technologies in testing skills . But because it involves other skills of the whole test system , So the understanding of use cases , In fact, it is the testers' understanding of testing . If you find that you can't write better use cases , See more business-related information , At the same time, learn the testing process , Involve your own testing ideas in the corners of related businesses , And integrate it into the actual test process . At this time, you will find that there is much room for improvement in the previous test case design idea , Gradually, we can start to analyze and test the environment （ It's not just about executing the test environment ）, Master the test framework , Develop test strategy . The lack of foothold in the previous design of use cases , It will be supplemented accordingly . justified , Naturally, the logic of use case design is clear .

Source of the article ： The Internet The copyright belongs to the original author

The above is not for commercial purposes , If it involves intellectual property , Please contact Xiaobian , We will deal with it immediately