Fault Masking is

[jainbrijesh]

Fault Masking is

a. Error condition hiding another error condition
b. Creating a test case which does not reveal a fault
c. Masking a fault by developer
d. Masking a fault by a tester

[vijaya09]

Error condition hiding another error

[sridharrganesan]

Fault Masking is a Error condition hiding another error Condition.

Fault masking is a redundancy technique that completely masks faults within a set of redundant modules (the modules which are redundant in properties). After the faults are masked then the number of identical modules which execute the same functions, and their outputs are selected to remove errors created by a faulty module.

[ashwani.sahu]

Masking a fault by developer

Please reply whether it is right.

[deepasree]

hi jain

According to me the answer is "Error condition hiding another error condition"

Thanks
Deepasree

[ssauradi]

"Error condition hiding another error condition" is the correct Answer

[SamerDesouky]

Fault Masking is an occurrence, in which one defect prevents the detection of another,

It’s a used technique to prevent error result from appearing.

For example, if the “Negative Value” cause a system unhandled exception firing, the developer prevents the negative values input instead to handle it, implicitly it solve the issue and prevent another defect from appearing but explicitly if the values entered manually in the database and the system goes to retrieve it, an unhandled exception may fires.

So, as a test engineer you can uncover it by using the Grey Box techniques by inter the data manually in the database and try to retrieve it by the application.

And it can be uncovered by executing a test case which created based on an Equivalence Partitioning design technique.
For more information please contact me.

Samer Desouky,
Test Leader, MCS