In the MASPAR case study:
-
Security failures were the result of untested parts of code
-
The development team achieved complete statement and branch coverage butmissed a serious bug in the MASPAR operating system
-
An error in the code was so obscure that you had to test the function with almostevery input value to find its two special-case failures.
-
All of the above.
Reveal answer
Fill a bubble to check yourself
C
Correct answer
Explanation
In the MASPAR case study (frequently cited in software testing curricula), the main conclusion is that an error in the code was extremely obscure, requiring testing of nearly all input values to detect two specific edge-case failures. This demonstrates the limitation of standard coverage metrics, as structural coverage alone cannot guarantee the absence of such data-specific bugs.