Software testing interview question: what do you think is the key to good test case design?

What do you think is the key to do a good job in test case design ?

The key of white box test case design is to cover as many internal program logic structures as possible with fewer use cases . The key of black box test case design is also to cover module output and input interfaces with fewer use cases . It's impossible to do a full test , Find the most problems in a reasonable time with the least use cases . The black box test of software means that the test should be carried out at the interface of the software , This method regards the test object as a black box , Testers don't consider the logical structure and internal characteristics of the program at all , Only according to the requirement specification of the procedure , Check whether the function of the program conforms to its function description . Therefore, black box testing is also called function testing or data-driven testing . The main purpose of black box testing is to find the following types of errors ：、

　1- Is there any incorrect or missing function

　2- On the interface , Whether the input can be accepted correctly ? Can you output the correct result .

　3- Is there any data structure error or external information ( For example, data files ) Access error

　4- Whether the performance can meet the requirements

　5- Whether there are initialization or termination errors

　 White box testing of software is a detailed examination of the process details of the software . This approach treats the test object as an open box , It allows testers to take advantage of the logical structure and information inside the program , Design or select test cases , Test all logical paths of the program . By checking program status at different points , Determine whether the actual state is consistent with the expected state . Therefore, white box testing is also called combination testing or logic driven testing . White box test is mainly to check the program module as follows ：

　1- Test all independent execution paths of program modules at least once .

　2- For all the logical decisions , take “ really ” And take “ false ” Both of them can be tested at least once .

　3- Execute the loop body within the bounds of the loop and the bounds of its operation .

　4- Test the effectiveness of the internal data structure , wait .

---

Personal profile

I am a test and Development Engineer , at present 25K, What we are doing now is driverless , Welcome to share the development and testing technology with you , High paying employment together , We also have a group to fight monsters together , And the interview question applet !