How can we help?

You can also find more resources in our Help Center.

Testing throughout the software life cycle

Learning objectives for testing throughout the software life cycle The objectives identify what you will be able to do following the completion of each module. According to ISTQB Foundation 2007.
STUDY
PLAY
Software development models
LO-2.1.1 Understand the relationship between development, test activities and work products in
the development life cycle, and give examples based on project and product
characteristics and context (K2).
LO-2.1.2 Recognize the fact that software development models must be adapted to the context
of project and product characteristics. (K1)
LO-2.1.3 Recall reasons for different levels of testing, and characteristics of good testing in any life cycle model. (K1)
Test levels
Compare the different levels of testing: major objectives, typical objects of testing, typical targets of testing (e.g. functional or structural) and related work products, people who test, types of defects and failures to be identified. (K2)
Test types
LO-2.3.1 Compare four software test types (functional, non-functional, structural and changerelated)
by example. (K2)
LO-2.3.2 Recognize that functional and structural tests occur at any test level. (K1)
LO-2.3.3 Identify and describe non-functional test types based on non-functional requirements.
(K2)
LO-2.3.4 Identify and describe test types based on the analysis of a software system's structure
or architecture. (K2)
LO-2.3.5 Describe the purpose of confirmation testing and regression testing. (K2)
Maintenance testing
LO-2.4.1 Compare maintenance testing (testing an existing system) to testing a new application
with respect to test types, triggers for testing and amount of testing. (K2)
LO-2.4.2 Identify reasons for maintenance testing (modification, migration and retirement). (K1)
LO-2.4.3. Describe the role of regression testing and impact analysis in maintenance. (K2)