14/06/2022 08:50:19 AM
Kinh nghiệm - Thủ thuật
Integration Test Planing
Integration test must be planned. Planning can begin when high-level design
is complete so that the system architecture is defined. Other documents
relevant to integration test planning are the requirements document,
the user manual, and usage scenarios. These documents contain
structure charts, state charts, data dictionaries, cross-reference tables,
module interface descriptions, data flow descriptions, messages and event
descriptions, all necessary to plan integration tests. The strategy for integration
should be defined. For procedural-oriented system the order of
integration of the units of the units should be defined. This depends on
the strategy selected. Consider the fact that the testing objectives are to
assemble components into subsystems and to demonstrate that the subsystem
functions properly with the integration test cases. For object-oriented
systems a working definition of a cluster or similar construct must
be described, and relevant test cases must be specified. In addition, testing
resources and schedules for integration should be included in the test plan.
» Tin mới nhất:
- 10 Kinh Nghiệm & Thủ Thuật Giúp Bạn Làm Chủ Phần Mềm Hiệu Quả Hơn (17/07/2025)
- CÁCH CHUYỂN ĐỔI PROJECT TỪ JAVA ANT SANG JAVA MAVEN (18/05/2025)
- Làm thế nào để trở thành Java Developer giỏi (17/01/2025)
- Phương pháp học và tự học (18/12/2024)
- Tìm hiểu về Custom button trong Android (10/12/2024)
» Các tin khác:
- Designing Integration Tests (14/06/2022)
- Integration Strategies for Classes (18/05/2022)
- viết hàm lấy dữ liêu trong ADO (18/05/2022)
- Levels of Testing and the TMM (12/04/2022)
- The Test Harness (15/03/2022)
- Sử dụng biểu thức ràng buôc dữ liệu data-binding trong ASP.Net (17/01/2022)
- The Retesting of Classes (13/01/2022)
- Điều khiển nguồn dữ liệu trong ASP.Net (18/12/2021)
- The C++Test Solution: Automated Unit Testing (16/12/2021)
- Levels of Testing and Software Development Paradigms (18/11/2021)
