Review of Software Testing (II.)

The fourth Chapter system test

1. Functional Testing

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 testing

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

4. Smoke test, stress test

5. Capacity Testing

6. Robustness testing: Ability to withstand errors, auto-recovery or ignore failures

7. Security testing: The ability to defend against illegal intrusion

8. Reliability Testing

9. Recovery and backup testing: fault tolerance

10. Protocol Conformance testing: strict adherence to protocol descriptions

11. Compatibility test: Compatibility between software

12. Installation testing: Verify the ability to successfully install and work properly after installation

13. Usability testing

14. Configuration test: Works correctly under different configurations

15. Document testing: User documentation, developing documents, managing documents

16. Acceptance Testing

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

17. Regression test: Changes to ensure the original function

18. System Testing Process

P System test Plan

D Design System test Cases

C Review and approval system test

A Perform system test

Chapter Fifth Unit Testing

1. Objective: To verify that code conforms to design, tracks requirements and design implementations, discovers errors in design and requirements, and discovers errors introduced in the coding process.

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 tests)

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

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

Sixth Chapter Integration test

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

2.. Level of integration testing: traditional software Engineering (inter-module, intra-subsystem, subsystem)

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

3.. Strategy: Non-incremental integration: Test each sub-module first, then integrate it all at once

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: Run for the system, forward testing, reverse testing, to meet special needs, design use cases for coverage

Review of Software Testing (II.)