Which of the following should NOT normally be an objective for a test?
-
To find faults in the software.
-
To assess whether the software is ready for release.
-
To demonstrate that the software doesn’t work.
-
To prove that the software is correct.
Testing can show the presence of defects but cannot prove their absence or that software is entirely correct. Finding faults, assessing release readiness, and demonstrating failures are standard testing objectives, whereas proving absolute correctness is mathematically and practically impossible.
To answer this question, you need to understand the objectives of software testing. Let's go through each option to understand why it is correct or incorrect:
Option A) To find faults in the software - This option is a valid objective for software testing. The purpose of testing is to identify and discover defects or faults in the software.
Option B) To assess whether the software is ready for release - This option is a valid objective for software testing. Testing helps to determine whether the software meets the required quality standards and is ready for release.
Option C) To demonstrate that the software doesn't work - This option is not a typical objective for software testing. The primary goal of testing is to identify faults, not to demonstrate that the software doesn't work.
Option D) To prove that the software is correct - This option is incorrect. It is not feasible to prove that software is completely correct through testing alone. Testing can help identify faults, but it cannot guarantee that the software is entirely error-free.
The correct answer is D. The objective of testing is not to prove the software is correct but to identify faults and assess its readiness for release.