Some terms in the test
Author: Alan
Key words: unit test, white box test, system test
For test terms, test engineers who are initial in this way often confuse some important concepts.
Even the old birds who have been tested for several years, similar errors are also uncommon. Let us review some common understanding errors together.
1. Unit test and white box test
It is the most common error with the unit test with the white box test. In the eyes of many people, the white box test seems to be unit testing, and there is a equal number between the two. This idea is also common in programmers. So what is the difference between unit testing and white box testing?
The concept of Unit Test originated in the Structured Test Theory. For this classic model, everyone is also familiar, it is a test for the work phase of the code, which corresponds to the design of the design integration test and demand system testing. Although there are currently a lot of test hierarchy models, it is based on traditional V test models. So in this sense, the unit test is essentially a level of lower level (Low Level), which reflects the test level information. Programmers often do some unit tests in daily development, but we don't realize it.
White box testing is a test method for the logical structure inside the subject, the architecture. From the definition to see the white box test is a method of testing, that is, it is a universal applicable methodology. In the test, we can use white box technology in system testing to design test cases. Also in unit tests can also use black box methods to design tests, such as testing a function interface, we only consider the correspondence between input values and output, which is a typical black box test method.
Unit testing and white box testing is two different concepts, which should be distinguished in use.
2. System Test, Pressure Test, Performance Test
Pressure test, performance test is a common test type (TYPE), system test is the highest level test. There is still a significant difference between the two. Due to the pressure test, performance test is for the entire system, and the premise of test execution is that the entire system is completed, so pressure testing and performance test belong to the category of system testing. However, the situation of confusing between the three often occurs. In some test plan templates and test strategies on the network, system testing, pressure testing, and performance testing are often tested as the same level of testing or as the same type of test.
3. Validation and Verification (Verify)
Validation and Verification are both test engineers' job responsibilities (work content), because both are often translated into the same word because both reasons are translated - confirmation. It is precisely because of this translational deviation, and many testers have made mistakes.
Validation is concerned about Are We do Right Things? That is, what we expect, such as demand is not implemented.
Verification is concerned about whether the method of doing things is correct, that is, the implementation method is correct.
As a test engineer, you need to consider problems from this two aspects when designing test cases. The daily ignored is verification, which is to verify that the implementation method is correct. The error implementation method is in a certain input field, the output domain is correct. However, on the entire input collection, an error can produce an error, such as boundary value analysis is a common method for designing such problems.
The test concept is very important for test engineers. Whether it is testing exchange or understanding of the test, the conceptual understanding of the correctnessless deviation is crucial. For engineers who have just been tested, I recommend a book: Testing Computer Software (KANER), the name of Chinese is software test. The term is very clear in the test, which is very clear, and it is a good entry reading.
-------------------------------------------------- --------------------------------------[About the Author]
Name: alan
Research direction: software engineering and theory.
Hobbies: sports, music, climbing.
Email: alanker@sohu.com.
Location: Shanghai
