Fault Masking is
-
Error condition hiding another error condition
-
Creating a test case which does not reveal a fault
-
Masking a fault by developer
-
a fault by a tester
Fault masking occurs when one error condition prevents detection of another error, for example, a bug in exception handling code that masks the original exception, or incorrect error handling that hides the true failure. Option A directly defines this. Creating ineffective tests (B) or hiding faults intentionally (C) are different concepts.
Fault masking occurs when one error condition prevents another underlying error from being noticed or reported, effectively hiding it during testing or execution. This is distinct from simply writing a weak test case that fails to reveal a fault, or from a fault being intentionally concealed by a person — masking specifically refers to one fault's effect obscuring another's.