Title CH01_TXT02_what is testing.pdf ✅

What Is Testing (K2) Objectives: 1.2.1 Recall the common objectives of testing (K1) 1.2.2 Provide examples for the objectives of testing in different phases of the software life cycle (K2) 1.2.3 Differentiate testing from debugging (K2) Terms: Debugging – Requirement – Review - Test case – Testing - Test objective 1.2.1 objectives of testing (K1) • A common perception of testing is that it only consists of running tests, i.e., executing the software. • This is part of testing, but not all of the testing activities ساليدTest activities exist before and after test execution which includes • Planning ,control, • Choosing test conditions • Designing and executing test cases • Checking results • Evaluating exit criteria, • Reporting on the testing process and system under test • Finalizing or completing closure activities after a test phase has been completed. • Testing also includes reviewing documents (including source code) and conducting static analysis. • Both dynamic testing and static testing can be used as a means for achieving similar objectives, and will provide information that can be used to improve both the system being tested and the development and testing processes. • Testing can have the following objectives: 1. Finding defects 2. Gaining confidence about the level of quality 3. Providing information for decision-making 4. Preventing defects • 1.2.2 examples for the objectives of testing in phases of the software life cycle (K2) • The thought process and activities involved in designing tests early in the life cycle (verifying the test basis via test design) can help to prevent defects from being introduced into code. • Reviews of documents (e.g., requirements) and the identification and resolution of issues also help to prevent defects appearing in the code. • Different viewpoints in testing take different objectives into account. • For example: • in development testing (e.g., component, integration and system testing), the main objective may be to cause as many failures as possible so that defects in the software are identified and can be fixed. • In acceptance testing, the main objective may be to confirm that the system works as expected, to gain confidence that it has met the requirements.