2022 software test interview questions 200 big factory interview true questions brushed to get 10K positions

List of articles

Tips ： Before reading this chapter , Please read the catalogue first

---

---

Preface

software test ,200 A real test interview question

---

1. When writing test cases , What methods are usually used to design test cases ？

At work , The method I use most is , The boundary value , Equivalence class , Scene method

The first one , It's the boundary value , Feedback on my testing experience , A large number of errors between software programs , The error on the input side , Most of it is because the input or output is on the boundary of the range , such as , An integer is greater than 0, Less than or equal to 5, that , We can get some values , Namely -1,0,1,4,5,6, that , These values are a boundary of the values we are currently entering , Then we can design test cases based on these values .

the second , Is equivalent class , It can be divided into effective equivalence classes , And invalid equivalence classes , In a subset of our input range , It is positive for software program operation , Then it is the effective equivalence class , And beyond this subset of the scope , Is beyond the scope of programming , Is an invalid equivalence class .

Third , Scene method , It is to sort out all the business processes of the system , Then the branches of each business process are sorted out , then , We sort out the positive process , And after the reverse process , Let's design the test behavior that we may experience in each process ？ In the middle of the process , What kind of data can we input , perhaps , What kind of operation to perform , You can go to other processes , Then go to the normal process , Let the whole process run through . Scene method , We will combine the design method of boundary value and equivalence class , To have a comprehensive coverage test of our system .

2. During the test , Why do interface tests ？

Why should we conduct interface testing , I have summed up four points

The first one is , When we do functional testing , It is often only for the function test of the front-end page , Even if the front end has relatively good data format verification , But you can use some tools , To bypass our front-end verification , Call the interface directly , such , It will lead to , The verification of our front page is completely invalid , therefore , We need to test the interface , Bypass the front end , Directly verify the interface , To find what you can't find on the page BUG.

The second one is , Check the system's ability to handle exceptions , For interfaces , If you pass in some abnormal data , Whether it will cause the server to crash , This leads to some code leaks , therefore , Conduct interface test , It's very necessary .

The third is , Check the security of the system , We know , There will be many hackers attacking servers maliciously in the Internet , Lead to data leakage , Some injection attacks , Code review, etc , If , Our interface does not handle these malicious attacks , that , It may lead to our system being attacked and invaded , Thus leading to direct economic losses , therefore , For interface testing , To check the security of our system to a certain extent .

The fourth is , Ensure the quality of the server , Avoid our version update iterations , It will lead to the instability of the server , When we call the interface at the front end , It needs to return a stable processing result , Otherwise , It will also lead to the instability of the front-end function , therefore , To ensure the stability of front-end functions , You need to ensure the quality of the server .

---

Update log

Tips ： Will continue to optimize and update

20220727, Interview questions #1,