Tag: testing

Questions Related to testing

  1. Is the same as equivalence partitioning tests

  2. Test boundary conditions on, below and above the edges of input and output equivalence classes

  3. Tests combinations of input circumstances

  4. Is used in white box testing strategy


Correct Option: B
  1. System testing

  2. Usability testing

  3. Performance testing

  4. Both b & c


Correct Option: D
  1. Data tester

  2. Boundary tester

  3. Capture/Playback

  4. Output comparator


Correct Option: C
  1. Statement Coverage

  2. Pole Coverage

  3. Condition Coverage

  4. Path Coverage


Correct Option: B
  1. Functionality

  2. Usability

  3. Supportability

  4. Maintainability


Correct Option: C
  1. Quality is job one

  2. Zero defects

  3. Conformance to requirements

  4. Work as designed


Correct Option: C
  1. Error condition hiding another error condition

  2. Creating a test case which does not reveal a fault

  3. Masking a fault by developer

  4. Masking a fault by a tester


Correct Option: A
Explanation:

To understand this question, the user needs to know the basic concept of software testing. Fault masking is a technique used in software testing to hide one fault by another one, which makes it difficult to identify the original fault.

Now, let's go through each option:

A. Error condition hiding another error condition: This option correctly defines fault masking. It means that one error condition is hiding another one.

B. Creating a test case which does not reveal a fault: This option is incorrect. It defines a technique called "passive testing," where the tester creates a test case that does not reveal any faults. It is not related to fault masking.

C. Masking a fault by developer: This option is incorrect. Developers write code to fix faults, not mask them.

D. Masking a fault by a tester: This option is incorrect. Testers are responsible for identifying faults, not masking them.

Therefore, the correct answer is: A. Error condition hiding another error condition.

  1. Lack of technical documentation

  2. Lack of test tools on the market for developers

  3. Lack of training

  4. Lack of Objectivity


Correct Option: D
  1. When the code is complete

  2. When the design is complete

  3. When the software requirements have been approved

  4. When the first code module is ready for unit testing


Correct Option: C