Dynamic Testing

Introduction

Dynamic method refers to performance of operational results and expected results by running the measured procedure, and analyzes the performance of operational efficiency and robustness. This method consists of three parts. : Construct the test instance, execute the program, the output result of the program.

The dynamic test of the so-called software is to verify the dynamic behavior of the software and the correctness of the operation results. At present, dynamic testing is also the main way of the company's testing work.

Step

Dynamic test can be divided into the following steps based on the stage and effects of the dynamic test in the software development process:

unit test < / h3>

unit testing is a testing of basic components in the software, the purpose is to verify the correctness of the software basic components. In the company's quality control system, the unit test is completed by the product group before the software submitted the test department. The unit test is a white box test.

White box test is also known as structure test, transparent box test, logical drive test, or code-based test. White box test is a test case design method. The box refers to the software being tested. The white box refers to the box is visible. You know how the box inside and how it works. "White Box" method fully understands the internal logical structure of the program and tests all logical paths. "White Box" method is exhausted path test. When using this scenario, the tester must check the internal structure of the program, from the checkpoint logic, to draw test data.

Integrated Test

Integration test is a test conducted during the software system integration, and its main purpose is to check that the interface between the software unit is correct. In actual work, we divide the integrated test into several assembly tests and confirmation tests.

assembly test is an extension of the unit test, except for the test of the software basic components, also needs to increase the interface of the interface between the interconnected module. For example, in the three-dimensional calculation software, component arrangement and component engineering calculations are different components of software, but the data calculated by component engineering is directly derived from component arrangement, and both of them are individually tested, which may be normal, but component arrangement Whether the data can be passed normally to the quantity calculation, the test must be inspected by the assembly test. The integrated test is a white box test.

Confirmation test is a test of assembly test results, the main purpose is to rule out the unit test as much as possible, and the errors found in the assembly test.

System Test

System Test is a thorough test for the already integrated software system to verify the correctness and performance of the software system to meet the requirements specified by its statutes. System testing should be carried out in accordance with the test plan, its input, output, and other dynamic operational behavior should be compared with the software statute while testing the strongness and ease of use of software. If the Software Statute (ie software design manual, software demand manual, etc.) is incomplete, system testing is more dependent on test staff's work experience and judgment, such testing is insufficient. The system test is a black box test.

Acceptance test

This is the final test before the software is put into use. It is the trial process of the buyer's software. In the actual work of the company, it is usually used to trial or publish BETA software to implement. The acceptance test is a black box test.

Black box test is also known as functional testing, which is tested to detect if each function can be used normally. In the test, the program is regarded as a black box that cannot be opened. When the internal structure and internal characteristics are completely not considered, it tests in the program interface, which only checks whether the program function is used in accordance with the requirements of the requirements specification, Whether the program can properly receive input data to generate the correct output information. The black box tests the external structure of the program, regardless of the internal logic structure, mainly for the software interface and software function.

The black box test is tested from the user's point of view, from the corresponding relationship between input data and output data. Obviously, if the external feature itself has a problem or specifications, it is not possible to use the black box test method.

Return test

is a software maintenance phase, its purpose is to verify and modify the acceptance test results. In practical applications, the processing of the cheek is an embodiment of the regression test.