Differences between system testing and integration testing

The general small system distinction is not very large

1. Sequencing of plans and use-case preparation
From the V model, in the requirements phase to develop system test plans and use cases, when HLD to do integration test plans and use cases, some companies are specific practice is not the same, but Shun
The preface must be to do the system test plan use case first, then do integration

2. The granularity of the use case
System test cases are relatively close to user acceptance test cases
Integrated test cases are more detailed than system test cases, and focus on the interface part, after all, to integrate modules or subsystems

3. Sequence of tests performed
Perform the integration test first, after the problem is repaired, (configuration management, Baseline), and then do system testing.

4. Number of Use cases
The number of use cases for system testing is generally less than the number of use cases for integration tests, the specific quantity is determined according to the performance baseline of each company, and it is not generally written in this number of test cases. Audit

System testing this term is often used in stress testing, capacity testing, performance testing, security testing and so on.

The term integration test is often used in the hyper-set of detailed functional tests that design and organize larger granularity of functional testing from the user's needs.

System testing is the most important function test, test software "Requirements Specification" mentioned in the function is missing, whether the correct implementation. To do system testing in strict accordance with the "Requirements Specification", to it as a standard. Test methods are generally used black box test method;
Integration tests are tested when the system is integrated after the unit test is completed before the system is tested. Integration testing is mainly testing the internal structure of the program, especially the interface between programs. Integration testing requires a higher ability to write scripts for testers. Test methods are generally selected with black box test and white box test combined.

Integration testing: A test performed during the integration of software systems, whose primary purpose is to check whether the excuse between the software units is correct. It is based on an integrated test plan that combines modules or other years of units into an increasingly large system, running the system to analyze whether the system is correct and each component is in sync. The strategies for integration testing are mainly Top-down and bottom-up. Can also be understood in the Software Design unit, when the function module is assembled and set into a system, the joint test of the components of the application system (software Unit, Function module interface, link, etc.) is made to determine whether they can work together, and the part may be a code block, a stand-alone application, a client on the network or a server-side program.


System test: System test is based on the software requirements manual black box test, is the integrated software system thoroughly tested to verify the correctness and performance of the software system to meet the requirements of its specifications, check the software's behavior and output is correct, not a simple task, The "Prophet Problem", known as testing. Therefore, the system test should be carried out according to the test plan, and its input, output and other dynamic behavior should be compared with the software specification. Software system testing methods are many, mainly functional testing, performance testing, random testing and so on. In layman's terms, a product from research and development to the factory project, the test is divided into three stages: unit test, integration test, System test, Unit test: A function of a module and general error test, integration test: After unit test, the modules are tested together, the interfaces of each module are unified, Whether the data flow between each module and the control of sulfur are implemented according to the design function, and the correctness of the result is validated, etc., it can make the whole product integrated test, also can make the big module integration test; System testing: Comprehensive testing for the entire product, It includes both the validation tests for each module (verifying the correctness of the first two phases of testing) and the functionality (the product submits a user's functionality) test, as well as the robustness, security, maintainability, and testing of various performance parameters for the entire product