Software Testing Fundamentals (ii) test methods

Software testing methods look at a number of ways to define them from a different perspective.

Static & Dynamic Partitioning

Static tests include code checking, static structure analysis, code quality metrics, and so on. Code inspection includes code walk, desktop inspection, code review, and so on, mainly check the consistency of code and design, code adherence to standards, readability, the logical expression of code correctness, the rationality of code structure, etc. can be found in violation of the program writing standards, the program is unsafe, ambiguous and vague parts, Find out the non-portable parts of the program and violate the programming style of the program, including variable checking, naming and type review, grammar checking and program structure checking. In practice, code checking is more effective than dynamic testing, can quickly find defects, discovers 30~70% logical design and coding flaws, and code inspection sees the problem itself rather than the symptom. But code checking is time-consuming, and code checking requires the accumulation of knowledge and experience. The code review should be done before compiling and dynamic testing, and should be prepared with requirements description documentation, programming documentation, program source list, Code coding standards, and Code defect checklist before checking. Static testing has the advantage of discovering defects early, reducing rework cost, covering emphases and discovering the probability of defect, the disadvantage is time-consuming, high technical ability, and can not test dependence.

Dynamic testing refers to the difference between running results and expected results by running the program under test, and analyzes the operational efficiency and robustness, which consists of three methods: constructing the test instance, executing the program, and analyzing the output result of the program. Currently dynamic testing is also the main way for most companies to test their work.

"Box" division

The software testing method can be divided into white box test and black box test traditionally. The simplest difference between the so-called white box or black box is whether the program source code is visible to the tester.

White box test

Also known as structural testing, transparent box testing, logic-driven testing, or code-based testing. The White box method thoroughly understands the internal logic structure of the program and tests all logical paths. The White box method is a poor lift path test. When using this scenario, the tester must examine the internal structure of the program, starting with the logic of the checker and drawing the test data. White box testing methods include API testing, code coverage testing, error injection testing, program mutation testing, and static testing.

The coverage criteria for white-box testing are logic overlay, loop overlay, and basic path testing. The logic overrides include statement overlay, decision overlay, conditional override, decision/condition overlay, conditional combination override, and path overlay.

Black box test

Black-Box testing is also known as functional testing, and it is tested to see if each feature is working properly. In the test, the program is considered a black box can not be opened, regardless of the internal structure of the program and internal characteristics of the case, in the program interface testing, it only checks whether the program according to the requirements of the specification of the normal use, the program can properly receive input data and produce the correct output information. It is mainly tested for software interface and software function. Black box testing methods mainly include equivalence class partitioning, boundary value analysis, decision table method, causality Diagram method, module test, fuzzy test, use case test, exploratory test and test according to requirement specification.

Grey Box test

Gray box testing, is between the white box test and black box test, it can be understood that the gray box test is concerned about the correctness of output for input, but also pay attention to internal performance, but this concern is not as detailed and complete as the white box, but through a number of representational phenomena, events, signs to determine the internal operating state, sometimes the output is correct , but the internal is actually wrong, this situation is very much, if every time through the white box test to operate, the efficiency will be very low, so need to take such a gray box method.

Software Testing Fundamentals (ii) test methods