What is a successful Test?
-
A successful test is one that finds no bugs
-
A successful test is one that finds a fault
-
A successful test is one that creates no results
-
A successful test is one that finds a failure
A successful test is one that reveals a fault in the software (B). This is a fundamental testing principle - tests that find defects are more valuable than tests that pass without finding issues. Option A (finds no bugs) describes a failed testing effort from a quality assurance perspective. Option D (finds a failure) is a consequence, not the test's success measure.
In classic software testing philosophy (Glenford Myers), the purpose of testing is to find defects, so a test that actually uncovers a fault is considered successful — it did its job of exposing a problem before the user does. A test that finds nothing hasn't demonstrated much value, since the absence of failures could just mean the test wasn't rigorous enough to expose an existing bug.