Masked Defect In Software Testing

September 05, 2019

---

Among the numerous defects detected by the team during software testing, there are a few that easily pass the test and stay hidden in the software even after its release, until some unexpected scenarios or inputs are implemented by the user, in the real-world environment. These defects are known as unusual defects, which are of three types:

1. Latent Defect.
2. Masked Defect.
3. Defect Cascading.

Masked Defect is one of these unusual defects, which will be discussed in detail below.

What is the Masked Defect in Software Testing?

Masked Defect is a type of defect that is hidden in the software and hasn’t caused a failure, because another defect has prevented that part of the code from being executed. It is only uncovered when the defect hiding it is uncovered by the user, by performing a specific operation.

In short, Masked defects are the defects covered by or marked by another defect and can’t be identified until the latter is detected.

Masked Defects Example:

One of the most simple examples of Masked Defects can be observed on page navigations. When there is an issue or defect in one page, it prevents the team to move from that page to another. This further inhibits the team from identifying defects in other pages.

Key Points:

• Masked defects are extremely difficult to identify.
• It can remain in the system forever until the defect covering it is uncovered.
• Usually hidden by latent defects.
• Does not impact the software’s functionality.
• Hides other defects in the system.

Maked Defect Infographics