Certified Associate in Software Testing (CAST) Practice Test

Why is the traditional view of testing at the end of the project problematic?

1. It allows for late detection of user needs

2. Errors found late increase overall costs

3. It requires more documentation

4. It leads to more debugging

The correct answer is: Errors found late increase overall costs

The traditional view of testing at the end of the project is problematic primarily because errors found late in the development process significantly increase overall costs. When defects are identified after a product has been fully developed, the cost of addressing these defects escalates. This is due to several factors, including the need to revisit and potentially overhaul design or coding work that has already been completed. Additionally, late-stage testing often requires more resources, such as time and personnel, to fix issues that could have been detected and resolved earlier in the development cycle. This late detection not only leads to increased expenses but can also impact project timelines and overall quality, as teams may rush to fix issues before delivery deadlines. A more proactive approach to testing, such as incorporating testing activities throughout the development process (like during the design and coding phases), helps identify and fix issues early, thereby reducing costs and avoiding the complications associated with finding defects later in the project.