After 10 years of summary and sharing with test engineers, an article will teach you how to quickly find bugs and write test cases

Software testing work to find bug It is the responsibility of this post itself , So for many new testers and newcomers , This process will be a little hard , After all, I don't have much project experience , Want to quickly cut in and find bug It's often painful .

Next, I will use my own experience to popularize how to quickly find out the deficiencies or defects of the system in my work .

1、 Be familiar with your products

No matter you are Dev、Test perhaps PM, The more familiar with the products developed by yourself, the better , You should not only be familiar with the modules you develop , You should also be familiar with other modules related to your own module , How they work together . For example, a field in the database , How to be used by each module , This is good for you to find Bug, Minimize the cost of repair .

Again , You need to be familiar with previous versions of this product , Because products that cannot be backward compatible and upgraded may be difficult to gain user recognition . During the test , If you find that your product is incompatible or inconsistent with the past ,80％ The situation of , This is a Bug.

2、 Find out as soon as possible Bug

We all know ,Bug The cost of repair is and Bug The time of being found is exponential . The sooner you start looking for Bug, You can find Bug The more , The greater the contribution to the project .

3、 Every day Review Others' Bug

If your team doesn't have daily Bug Report, I suggest you build a , In fact, there should be no technical difficulty , adopt Bug Tracking system API Or database , You can get the data you want , such , The whole team looks at other people's... Every day through learning Bug, You can find it easier Bug, I won't find that kind of Duplicated Bug. Now people often come over and ask me , Some Bug Is it a known problem , Because I watch it every day Bug Report.

4、 Prepare more test patterns in your daily life

Pattern is a very fashionable word , Because it's very useful . In daily tests , Prepare more test modes , You'll have a big surprise , Sometimes one uses one pattern , You can find 10 To a Bug It's not impossible . such as , Use special characters as input data ; Disconnect the network and see UI Whether it will Crash; In localized versions , Whether each string is localized ;

5、 Test the cooperation between various modules

The testing between various modules is often the weak point in our testing , For users, the cooperation between modules is very important . Often a data is in a module A Is legal , stay B It's illegal in , Be sure to find out these data , Often they are Bug

6、 Write automatic test code

You certainly don't want to do the same thing every day , That's too boring , It's an insult to your wisdom . But once we don't do these tests , Suddenly one morning , We found that the function of our product that used to work well suddenly stopped working , So everyone was in a mess , Someone is in a hurry to repair it , Someone is looking for who it is Check in Of .

7、 Check the product code

By looking at the product code , You can often find some Dead Code Or logical Bug, these Bug It's often something you can't find through manual testing .

Why write test cases

Why write test cases , In fact, there is a problem with the product , The first person in charge first thought about why the test didn't test ？

There's something wrong with the product , Why didn't you measure it ？

Of course , Except to avoid “ Toss and back ”, In fact, the more important role of writing test cases is as follows ：

• Technology transforms requirements into specific verifiable indicators
• Document possible problems with the software
• Prevent omissions from the activities of the test process , Improve work efficiency
• Demonstration of test workload

Test how new people write use cases ？

Many friends who are new to the testing workplace have just begun to write use cases , I don't know where to start , Although some companies have given relevant instructions and documents , But it's still not easy to write , There are many ways to write use cases ： Function oriented use cases （ The boundary value 、 Equivalence classes and so on ）, User oriented use cases （ Scene method ）, user 、 The combination of functions leads to use cases ……

So for new people writing use cases , How to write use cases efficiently ？ What should we pay attention to ？

One 、 Function oriented use cases refer to every function that the system needs to achieve , Write use cases , Such use cases focus on functional implementation , Without considering the relationship between each function , Thus, although the use case has reached functional coverage , But not necessarily achieve logical coverage , Therefore, this method is usually used in combination with other methods . Function oriented use cases are the most commonly used method in the early stage of each use case writer .

Two 、 User oriented use cases are based on user habits , Take each purpose of the user's use of the system as a goal , Design test cases based on the realization of each goal , But designing such use cases , First writer , There can be a lot of confusion （ Here are some puzzles when I first wrote , And address these puzzles , What kind of solution was adopted later ）

1、 The first step in writing use cases is what I should do ？

Understand the system , First, from the perspective of testing, deeply understand each function and business logic of the system , Draw the business logic diagram （ namely ： What can the system do ）.

Secondly, from the perspective of users , List the purpose of the user using the system （ namely ： Users use this system , What do you want to do ？）

2、 How to determine user goals ？

Unable to determine user goals , Maybe by 2 There are many reasons for :a> Not familiar with the system ,b> Don't know the user's background . For the first reason , That's your own reason , Only go back and look at the documents , For the second reason , It can be downloaded from ‘ What can the system do ’ Extrapolate ‘ What users can do ’ Then sum up ‘ What users may want to do ’, Of course, the premise of this is that you are already very familiar with the system .

3、 What will I do this month ？

How to sum up just entering the testing industry （ Summarize with test management tools ）：

1） Classify and export all the defects in the test management tool , Summarize which modules are prone to defects , Focus on the defects you didn't find or consider .

2） If the first level of testing is to start with the execution of use cases , Then the second level is to write test cases . Look at the use cases in the test management tool in detail several times , Learn other people's use case writing methods and ideas , In your spare time, you can try to write , Look at the gap between the use cases written by yourself and those written by others , So as to continuously improve . Important note ; Focus on the learning of use case writing methods and ideas , Don't copy the hard way .

3） Enter some test forums , Share your confusion and experience with you , In the study , Continuous improvement .

summary

The so-called Kung Fu is outside the poem , Testing theory is so much , After mastering the theoretical knowledge, we should continue to participate in the project , Practice one project at a time , Exercise your discovery Bug The ability of , Even a random test , A good test and a bad test , Their ability to find problems is also completely different . The above is a little personal insight , Dear reader , Please give me a lot of advice when reading .

In order to support new friends , Here I also share hundreds of learning materials and explanation videos compiled by the author for his testing career , Beginners can definitely use , It's all under it , I don't say much nonsense , Just join the technology sharing group ：769146372 Self mention link . Learning software testing is something to stick to , The learning process can be boring , But if some people learn together, they probably won't , Join us , Study with us , Accompanied , Not alone

The above information , It should be very helpful for small partners learning software testing , I hope it can help you .