Part 1 software R & D work summary
Integration Test
Abstr]
Generally, software R & D projects involve multiple modules and functions. After each module implements its functions, it is necessary to combine the relevant modules for integration testing to verify whether the entire system meets the requirements.
Based on the author's practical project experience, this article describes the entire integration test process and briefly introduces some common problems in the integration test process.
1. Preface
Most software developers may experience this experience during their work: they have implemented good functions in their own modules, and problems may occur once combined with other modules. Therefore, integration testing is very important. This is a bit like many domestic and international standards are not uniform. Before we leave the country, we must ensure that we are doing things in accordance with international standards, this saves a lot of trouble.
Many of my software projects contain many modules and have complex functions. After completing the predefined functions of each part, integrate all modules for integration testing. This not only discovers the shortcomings of this module, but also verifies whether the functions of the entire system can meet the requirements of customers. Integration testing is so important that it is an essential part in the project R & D process.
This article describes the entire integration test process in detail, and briefly describes some precautions and common problems during the test.
2. overall architecture and logic module of the project
The overall architecture and logic module 1 of the example in this article are shown.
Figure 1 overall architecture and logic module diagram
As shown in 1, the system involves four parts: AAA module, BBB module, CCC module, and database. The AAA module, BBB module, and CCC module provide relatively independent functions, but they all need to deal with databases.
It can be seen that the system involves many modules and complicated functions. It is necessary to test whether the overall function can meet the customer's requirements through integrated testing.
3. Integration Test Procedure
The integration test procedure is no different from the actual test procedure on site. Before testing, ensure that all modules required by the system are successfully built and that all configuration items in the relevant configuration file are filled in correctly.
The procedure 2 for this integration test is shown in.
Figure 2 integration test procedure
As shown in figure 2, the entire operation process is a link. After an operation fails, the entire integration test fails. To ensure the correctness of the system functions, you can perform multiple integration tests and use different data each time. In addition, if problems are found during the test, they should be promptly modified before testing.
4. FAQs about integration testing
During the integration test, the following are common questions and answers:
1) if the function execution of a module fails, is there a problem with the module?
A: Not necessarily. Because the test is performed on the entire system, if a module has a problem, you also need to check other modules.
2) if a problem is found during the integration test and can be changed to any module, how can we determine which module should be modified?
A: Generally, the principle we need to adhere to is to minimize the change and minimize the impact.
3) how to determine the integration test steps?
A: There are two methods: one is to test as needed, and the other is to test according to the system execution process. We recommend that you select the second method, which is more organized and can verify whether the entire process is correct.
5. Summary
This article mainly introduces the entire process of integration testing in actual software projects, and analyzes and answers common problems during the testing process.
The main purpose of the integration test is to ensure the quality of the Code and the quality of the system and product. After writing the code, developers must fully test the code and system to reduce the trouble caused by subsequent modifications.
(My microblogging: http://weibo.com/zhouzxi? Topnav = 1 & WVR = 5, No.: 245924426, welcome !)