What is dynamic testing?

What is dynamic measurement?

The dynamic method refers to running the program under test, checking the difference between the running results and the expected results, and analyzing the performance such as running efficiency and robustness. This method consists of three parts: constructing test instances, executing the program, and analyzing the output results of the program.

Steps of dynamic testing

The so-called dynamic testing of software is to verify the correctness of the dynamic behavior and running results of the software by running the software. At present, dynamic testing is also the main way of testing in the company.
According to the stage and role of dynamic testing in the software development process, dynamic testing can be divided into the following steps:
1. Unit testing
Unit testing is to test the basic components of the software, and its purpose is to verify the correctness of the basic components of the software. In the company's quality control system, unit testing is completed by the product group before the software is submitted to the testing department.
2. Integration testing
Integration testing is a test performed during the software system integration process, and its main purpose is to check whether the interface between software units is correct. In actual work, we divide integration testing into several assembly tests and confirmation tests.
Assembly testing is an extension of unit testing. In addition to testing the basic components of the software, it is also necessary to add testing of the interfaces between interconnected modules. For example, in the three-dimensional quantity calculation software, component layout and component quantity calculation are different components of the software, but the data of component quantity calculation comes directly from component layout. Both of them may be normal when unit tested separately, but whether the data of component layout can be normally passed to quantity calculation must be verified by assembly test. ?
Confirmation test is to check the results of assembly test, and its main purpose is to eliminate the errors found in unit test and assembly test as much as possible;
3. System test
System test is to thoroughly test the integrated software system to verify that the correctness and performance of the software system meet the requirements specified by its specification. System test should be carried out according to the test plan, and its input, output and other dynamic operation behaviors should be compared with the software specification, and the robustness and usability of the software should be tested at the same time. If the software specification (i.e. the software design specification, software requirement specification and other documents) is incomplete, the system test relies more on the work experience and judgment of the tester, and such test is insufficient.
4. Acceptance test
This is the last test of the software before it is put into use. It is the trial process of the software by the buyer. In the actual work of the company, it is usually achieved by asking customers to try or releasing Beta version of the software.
5. Regression testing
This is the software maintenance phase, and its purpose is to verify and modify the acceptance test results. In practical applications, the handling of customer complaints is a manifestation of regression testing.