Software testing is the key step of software quality control, which is the final review of software requirement analysis, design specification and coding before the software is put into production. Software Testing objects: Requirements analysis, summary design, detailed design and program coding and other stages of the documentation, including requirements specification, outline design specifications, detailed design specifications and source program. Confirmation is a series of activities and processes aimed at verifying the logical correctness of the software in an appropriate external environment, which is divided into static and dynamic acknowledgments. Verification is an attempt to prove the logical coordination, completeness and correctness of the various stages and phases of the software's life cycle. Validation and testing are software tests. Black box test: The functional design specifications of a known product can be tested to prove whether each implemented function satisfies the requirements (according to the external characteristics of the software) column design: A. Equivalence class partitioning; b. boundary value analysis. White box test: The internal working process of the known product can be tested to prove whether each internal operation conforms to the design specifications, and whether all internal components have been inspected (detailed examination of the process details of the software). Use case design: A. Logical coverage; B. statement coverage; c. coverage; d. conditional coverage; E. decision-condition coverage; F. conditional combination coverage; g. Path overlay. Software Testing: Steps: Unit Tests, assembly tests, validation tests, and system tests. Unit Test Content: module interface test, local data structure test, path test, error handling test, boundary test.
The core content of the sixth chapter of software engineering introduction