Types and principles of common tests

Black- box testing:

Black-box testing: Also known as functional testing, data-driven testing, or specification-based testing, is testing rigorously by using the entire software or a certain software function without examining the program's source code or It is very clear how the source code program of the software is designed. Testers learn how the software works by entering their data and seeing the output. It is not necessary for external testers to know how the program is implemented. White box testing: is testing the program's source code without using the user interface. This type of testing needs to find the shortcomings or errors of the internal code in algorithms, overflows, paths, conditions, etc. from the code syntax, and then correct them. For the tester, it is necessary to understand how the program is designed, just like deciphering. , to understand the internal principles of the direction and size of every blood vessel in the human body. Regression testing: Regression testing, the focus is on the back, refers to a program code, when adding new functions on the original basis, to test whether the previous functions are covered or affected, this process is called regression testing . Gray box testing Gray box testing is between white box testing and black box testing. It can be understood in this way that gray box testing focuses on the correctness of the output for the input, and also pays attention to the internal performance, but this focus is not like the white box. As detailed and complete, it only judges the internal running state through some representative phenomena, events, and signs. Sometimes the output is correct, but the interior is actually wrong. There are many such cases. If you pass the white box every time It will be very inefficient to operate by testing, so such a gray box method needs to be adopted. Unit testing: Unit testing is generally the code written by programmers when they write code and test their own functional blocks. Now the framework for unit testing is generally implemented by junit4. The purpose is to test whether the function block has achieved the target function. Black box testing is mainly to find the following types of errors: 1. Are there any incorrect or missing functions?




















2. Can the input be correctly accepted on the interface? Can it output the correct result?
3. Are there data structure errors or access errors to external information (such as data files)?
4. Can the performance meet the requirements?
5. Are there initialization or termination errors?


The main purpose of white box testing is to check the program module as follows:
1. Test all independent execution paths of the program module at least once.
2. For all logical judgments, the two cases of "true" and "false" can be tested at least once.
3. Execute the loop body within the bounds of the loop and the bounds of the run.
4. Test the validity of internal data structures, etc.


Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326442227&siteId=291194637