Unit testing, integration testing and system testing

System Testing

1. Function test

Analysis method: Marking each specific functional requirement, possible hidden function label, possible function marking, grading of functional requirements, analysis, scripting automation

Use case Design method: equivalence class division, boundary value analysis, causality diagram, decision table, error guessing method

2. GUI Test

Essential elements: compliance with standards and norms, intuition, consistency, flexibility, comfort, correctness, practicality

Category: Manual testing, automated testing

3. Performance test

Content: Assess the capabilities of the system, identify weaknesses in the system, and system tuning

4. Smoke Test and pressure test

5. Capacity Test

6. Robustness testing: Ability to withstand errors, automatic recovery or neglect of failures

7. Security testing: the ability to prevent illegal intrusion

8. Reliability Test

9. Recovery and backup testing: fault tolerance

10. Protocol conformance test: strictly follow the protocol description

11. Compatibility test: Compatibility between software

12, Installation test: Verify the ability to successfully install, whether the normal operation after installation

13. Usability Testing

14, the configuration test: in different configurations can work correctly

15. Document testing: User documentation, development documentation, management documentation

16. Acceptance Test

Strategy: Formal acceptance test, informal acceptance test, beta test

17, regression test: Change to ensure the original function

Unit Test

1, the purpose: To verify the code and design in line with, tracking requirements and design implementation, the discovery of design and requirements of the errors, the discovery of the coding process introduced errors

2. Environment: Test case Data--drive module--tested module (separate pile module)--Drive module

3, Method: Isolate the test strategy (global input variables, called functions, overlay test)

4. Test Case design: for system running and forward testing, for reverse testing, for code coverage

5. Process: Complete test plan, get test set, measure test unit

Integration Testing

1. Integration testing is the interface between test modules and data transfer

2. Level of integration test: Traditional software Engineering (inter-module, subsystem, subsystem)

Object-oriented (intra-class, inter-Class)

3. Strategy: Non-incremental integration: Test each sub-module first, then integrate it all in one test

Incremental integration: Divide the program into small pieces to construct and test: top-down (depth/breadth), bottom-up

Sandwich Integration: Integrated top-down and bottom-up

4, use case design: for the system to run, forward testing, for reverse testing, to meet the special needs, to cover the design of use cases

Unit testing, integration testing and system testing