Which of the following is a characteristic of good testing in any life cycle model?

Which of the following is a characteristic of good testing in any life cycle model?

• A. Analysis and design of tests begins as soon as development is completed.
• B. Some, but not all, development activities have corresponding test activities.
• C. Each test level has test objectives specific to that level.
• D. All document reviews involve the development team.

Answer: (C)

Good testing practices in any life cycle model emphasize that each test level should have specific test objectives that align with the goals and requirements at that level. This characteristic ensures that testing efforts are focused and effective, allowing testers to measure success against predefined criteria tailored to the context of each testing phase. When testing levels such as unit testing, integration testing, system testing, and acceptance testing each have their distinct objectives, it becomes easier to verify that the software meets the necessary quality standards and requirements at various stages. This clarity helps identify defects earlier and contributes to more efficient use of resources, as each level addresses different aspects of the software. Meanwhile, the other options present ideas that do not align with best practices in testing. For instance, starting test analysis and design only after development is complete can lead to delays and increases the risk of defects going unnoticed. Having test activities for only some development processes ignores the importance of comprehensive testing throughout the entire life cycle, and the notion that all document reviews involve the development team overlooks the collaborative nature of reviews that can include various stakeholders, not just developers.

Good testing practices in any life cycle model emphasize that each test level should have specific test objectives that align with the goals and requirements at that level. This characteristic ensures that testing efforts are focused and effective, allowing testers to measure success against predefined criteria tailored to the context of each testing phase.

When testing levels such as unit testing, integration testing, system testing, and acceptance testing each have their distinct objectives, it becomes easier to verify that the software meets the necessary quality standards and requirements at various stages. This clarity helps identify defects earlier and contributes to more efficient use of resources, as each level addresses different aspects of the software.

Meanwhile, the other options present ideas that do not align with best practices in testing. For instance, starting test analysis and design only after development is complete can lead to delays and increases the risk of defects going unnoticed. Having test activities for only some development processes ignores the importance of comprehensive testing throughout the entire life cycle, and the notion that all document reviews involve the development team overlooks the collaborative nature of reviews that can include various stakeholders, not just developers.