The process and strategy of software testing

A few days ago just finished testing software test, one of the questions is related to software testing strategy, personal feeling on this aspect is still relatively weak, therefore, want to take a summary of the software testing process and strategy.

First, the software testing process:

The process of software testing can be divided into four stages: unit test, integration test, validation test (validity test a test) and system test unit test for the minimum unit a program module of software design, test work for correctness test. It aims to discover the various error integration tests that may exist within each module on the basis of unit testing, and assemble all the modules into a system to be tested according to the design requirements. Validation tests (validation tests) Verify that the functionality, performance, and other features of the software are consistent with the user's requirements. System testing the software as a whole computer system as an element of the computer hardware, peripherals, some supporting software, data and personnel and other systems elements, in the actual operating environment, Assemble test and confirm test on computer system.

Second, the software testing strategy and process:

The strategy of software testing is to test what kind of ideas and methods will be used, such as what technology, what steps and so on. and software testing technology can be categorized in the following ways:

1. Black box (functional) Test and white box (structural) test:

(1) Black box test:

Black-Box testing is also known as functional testing, data-driven testing, and specification-based testing. It is aware of the software should have the function of the basis, check whether the program function in accordance with the requirements of the specification of the normal use, the function is missing, performance and other characteristics of the requirements are satisfied. In the case of black box testing, you only need to refer to the specifications to check the software, do not require inspection code, from the user's perspective to test the software. The purpose of the black box test is to detect whether the software function is correct and complete, to detect human-computer interaction and data access errors, to detect whether software behavior and performance meet the requirements, and to detect errors in the software initialization and final process.

Black-Box testing follow these steps: First, you need to generate the test case according to the specification, then perform the test and analyze the coverage criteria, and then make a conclusion based on the results obtained.

(2) White box test:

White-Box testing is also a structural test, a logic-driven test, a program-based test. The difference between it and the black box test is that we compare the execution performance of the program with the coding intent when we carry out the white box test, and we care about the internal design and the implementation of the software, and the main test is the code and design document, which can support strict definition, mathematical analysis and accurate measurement, so as to evaluate a software more accurately.

2, static testing and dynamic testing:

(1) Static test:

Static tests broadly include manual code checking, software metrics, program structure analysis (automatic review), and automatic programming rules to check for these contents.

(2) Dynamic test:

Dynamic testing includes coverage of test analysis and run-time error detection.

3. Traditional test methods and object-oriented testing methods:

(1) Road test:

Path testing is a technique for designing test cases on a path that is often used in state transition tests. The basic path test method is to design the test case by analyzing the loop complexity of control structure and exporting the basic executable path collection based on the program flow graph. The test cases are designed to ensure that the insulted executable statements of the program are executed at least once in the test.

(2) Data Flow test:

The previous test for the control flow path of the program, check the program in various condition values, various decisions whether the error data Flow test main test program of the numerical flow (overwrite the value of the pass path), detection of variable definition and use of the situation. It is easier to find the following types of errors: variables are defined, but never used, variables that are used are not defined two times before they are used, or otherwise improperly defined or improperly used.

(3) Facing the object software test:

The program developed by object-oriented technology needs to be tested and tested more complex. Object-oriented software and traditional software have different software structure, different development methods and each development stage have different requirements and results, for the new characteristics of object-oriented software, there should be a new test model.

4, the specific environment and application testing:

For object-oriented program software and specific environments based on client/server architecture, special testing methods are often required in addition to the methods of black-box and white-box testing. These tests are often considered to be carried out in the following areas: testing based on client/server architecture and operating environment, object-oriented testing, and real-time system-based testing.

The process and strategy of software testing