Software test interview questions (key points)

1. Tell me about a recent project ？

Refer to the answer ：1、 First tell the content in the project description , Then say the content in the responsibility description , Or describe the project in your own terms , Then say what you have done in this project , That is, the content of the responsibility description .

2. What is the testing process of the company ？

answer ： Project approval --（ To ） Requirements review — Make a test plan — Write test cases — Use case review — Optimize test cases — Entry iteration 1 Test version , Including assistance in development and modification bug、 regression testing ,– Output test report — go online .

3. How to define the indicators of project launch ？

answer ：bug The modification rate reaches 80%, All serious and fatal ones have been corrected , The rest are slight bug, After the meeting of the project team , It can be modified in the next version 、 to update , This version can be launched .

4. How long does the project go online ？

answer ： The first version 3 It has been online for more than a month , The subsequent iteration time is 1 to 2 About a month or so , Each update requires testing before it goes online .

5. What kind of development mode is used in the project ?

answer ： agile development , With the evolution of users' needs as the core , Use iterations 、 Step by step approach to software development .

6. Which project management system or defect management system is used ？

answer ： ZenTao

7.Bug What is included ？

answer ：bug title 、bug describe 、 Repeat step 、 The attachment （bug Screenshot ）、bug severity 、bug priority 、bug Designee 、 Affects version 、bug Type, etc .

8.bug The defect grades are divided into those grades ？

answer ： deadly 、 serious 、 commonly 、 Tips , Four levels .

9. Talk about that bug It's deadly ？

answer ： deadly （ Class A bug）, It is usually expressed as : The mainstream cannot run through , The system doesn't work , A breakdown or serious shortage of resources , Application module failed to start or exited abnormally , The main function modules cannot be used . such as ：1. Memory leak ;2. Serious numerical error ;3. The system is prone to crash ;4. The functional design is seriously inconsistent with the requirements ;5. The system can't log in ;6. Follow the bad and report the wrong , Can't exit normally .

10. To talk about that is serious ？

answer ： serious （ second level bug）, It is usually expressed as ： Affect the function or operation of the system , There are serious defects in the main functions , But it will not affect the stability of the system . such as ：1. Function not implemented ;2. There is an error in the function ;3. A slight miscalculation of the value .

11. To talk about that is general 、 Suggestive ？

answer ： commonly （ Level three bug）, It is usually expressed as ： Interface 、 Performance defects .
such as ：1. Error in boundary conditions ;2. Poor fault tolerance ;3. It's easy to be unresponsive under big data ;4. Big data operation , No progress bar provided .
Tips （ Level Four bug）, It is usually expressed as ： Ease of use and advice

12. The test case , What is included ？

answer ： The test case contains ： Number 、 Test module 、 Preset conditions 、 testing procedure 、 Expected results 、 priority 、 test result （pass/fail）

13. Test report , What is included ？

answer ： The test report contains ： Project name 、 brief introduction （1、 Purpose of writing 、2、 Project background 、3、 Reference material ）; Test summary （1、 Use case design method 、2、 Test environment configuration 、3、 Testing tools and methods 、4、 Test task progress ）; Test summary （1、 Demand coverage 、2、 Use case coverage 、3、 Defect summary and analysis 、4、 Test conclusion ）、 The attachment （1、 The test case 、2、 Defect list ）

14. What are the test documents ？

answer ： test plan 、 The test case 、 Test record 、 Test report, etc

15. What is included in the test plan ？

answer ： The test plan contains ： background 、 Project brief introduction 、 Purpose 、 Test range 、 The test strategy 、 Division of labor 、 Resource requirements 、 Schedule 、 Reference documents 、 Common terms 、 Submit documents 、 risk analysis

16. Talk about the characteristics of agile development ？

answer ： Agile development is characterized by a high degree of iteration , There is periodicity , And in time 、 Continuously respond to frequent customer feedback .

17. Talk about the characteristics of agile testing ？

answer ： Agile testing is the constant revision of quality indicators , Establish test strategy correctly , Confirm that the effective needs of customers can be successfully realized and ensure the safety of the whole production process 、 Timely release of final products .

18. What are the test methods ？

answer ： Black box testing 、 White box testing 、 Grey box testing

19. Talk about black box testing ？

answer ： Also known as data-driven testing , Treat the test object as an invisible black box , Without considering the internal structure and processing of the program , Testers only consider the requirements of the program function , Determine the correctness of test cases and inferred test results , It is from the perspective of using software or programs , Test based on the corresponding relationship between input data and output data .

20. Talk about the white box test ？

answer ： White box testing is also called structural testing 、 Transparent box test 、 Logic driven or code based testing . White box testing is a test case design method , Box refers to the software being tested , White box means that the box is visible , You know what's inside the box and how it works ." White box " Method to fully understand the internal logic structure of the program 、 Test all logical paths .

21. Talk about grey box testing ？

answer ： It's a comprehensive test , It will “ Black box ” Test and “ White box ” Tests are combined , It is based on the program runtime The external expression is combined with the internal logical structure To design use cases , Test technology of executing program and collecting path execution information and external user interface results .

22. What are the methods of black box design use cases ?

answer ： Division of equivalence class 、 Boundary value analysis 、 A false assumption 、 Cause and effect diagram 、 Decision table driven method 、 Orthogonal experimental design 、 Function diagram method 、 Scene method, etc . in addition , Division of equivalence class 、 Boundary value analysis 、 False speculation is the most common 3 Test methods .

23. What is equivalence class partition ？

answer ： The equivalence classification method is to divide all possible input data into several subsets , Then select a few representative data from each subset as test cases .

24. What is boundary value analysis ？

answer ： The boundary value analysis method is a supplement to the equivalent method , Is to select the test case of equivalence class boundary ; Boundary value analysis not only pays attention to the boundary of input conditions , And the boundary of the output domain must also be considered .

25. Let's talk about wrong conjecture ？

answer ： The error inference method is based on previous testing experience , Judge all possible errors in the program .

26. What are the white box test methods ？

answer ： Code checking 、 Static structural analysis 、 Static quality measures 、 Logical coverage 、 Basic path testing 、 Domain testing 、 Symbol test 、 Path coverage and program variation .

27. From which aspects to test ？

answer ： Function module test 、 Compatibility test 、 Install and uninstall test 、 Software update test 、 Performance testing 、 User experience testing 、 Cross event testing 、 User interface test, etc .

28. Talk about your most impressive or unforgettable bug？

Tips ： The interviewer's intention of asking this question is to know whether you have really tested this project ;
Refer to the answer 1： Shopping cart interface on Xiaomi mobile phone 6.0 The display on the version is abnormal , I was submitting bug When it's single , There is no comment on the version number of Xiaomi mobile phone , Development is repairing bug When , It uses Xiaomi mobile phone 7.0 Version of , When verifying the new version of regression, I found that this problem still exists , But the status is resolved , Just ask the developer to confirm this problem , Later, it was found that it was related to the version compatibility of the mobile phone , He that 7.0 There is no such problem in version , Only the mobile phone I tested has this problem ; So it's very profound , So submit bug Be sure to note this model and version number when you use , The follow-up can save everyone's time ;
Refer to the answer 2： Sometimes I mention something bug, The development side cannot reproduce , He will feel that there is no bug Or he changed other places , This bug No longer exists , And then he put bug The status of is changed to resolved , When it comes to regression testing , You find that the problem is still , Just put bug Activated , Sometimes several versions are like this , At this time, you still have to go to him personally to change , Or I'll forget again next time , They are too busy ;

29. Whole APP How many use cases have been written ？

Refer to the answer ：app Test cases in 3000 This range ;5 One test , Distribution is ios Development Engineer 3 individual 、android Development Engineer 4 individual 、 Database Development Engineer 2 individual 、 The background and development 2 individual ,web front end 3 personal ;

30. Who are the members of the whole project ？

answer ： project manager 、 The product manager 、UI The designer 、 Android 、IOS Development Engineer 、 Front end and background development engineer 、 Database Development Engineer 、 test , Some have operation and maintenance ;