Results 1 to 7 of 7

Thread: Fault Masking is

  1. #1
    Moderator
    Join Date
    Sep 2006
    Answers
    920

    Fault Masking is

    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

    Regards,
    Brijesh Jain
    ---------------------------------------------------------
    Connect with me on Skype: jainbrijesh
    Google Plus : jainbrijeshji

  2. #2
    Junior Member
    Join Date
    Dec 2007
    Answers
    3

    Re: Fault Masking is

    Error condition hiding another error


  3. #3

    Re: Fault Masking is

    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.


  4. #4
    Junior Member
    Join Date
    Aug 2008
    Answers
    1

    Re: Fault Masking is

    Masking a fault by developer

    Please reply whether it is right.


  5. #5
    Expert Member
    Join Date
    Apr 2008
    Answers
    1,859

    Re: Fault Masking is

    hi jain

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

    Thanks
    Deepasree


  6. #6
    Junior Member
    Join Date
    Aug 2009
    Answers
    2

    Re: Fault Masking is

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


  7. #7
    Junior Member
    Join Date
    Feb 2010
    Answers
    1

    Re: Fault Masking is

    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

    Last edited by admin; 02-28-2010 at 03:26 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact