Blog Archives

The most used defects classification is severity and priority.

So, What severity and priority:

• Severity: Is the impact that the defect has on the system
• Priority: Is the order in which defects need to be solved

I will explore this topic in a future post 😉

Hi guys,

Today I’m going to talk about a bug’s life cycle.

No QA likes to have defects in the code but unfortunately they do appear :(.

The life cycle of a bug is the journey of this little creature from its discovery to its elimination. The Life Cycle has some variations from organization to organization and it is generally influenced by the defect-tracking tool used.

Typically the bug life cycle has the following four phases: New, Open, Resolved and close.

 

New:

When the tester or a stakeholder finds a defect, a new bug is created on tool. It means that the bug has not yet been approved.

 

Assigned
Most companies don’t consider this phase as it is incorporated in the Open phase. In this phase the development leader confirms the veracity of the defect only.

 

Open: In this phase, verifying the veracity of the defect if necessary (refer Assigned phase). The developer reads the bug description and debug software to identify the bug that is causing the failure.

 

Resolved: The main objective of this phase is identifying that defects have been resolved and they can be retested.

 

Closed: After the bug is successfully retested, the bug is closed.

During the bug life cycle is important understand the following terms:

• Retest: QA activity, when the qa validate that bug was fixed. If the bug was fixed the bug state is change for resolved, if not the state is change for open.
• Closed loop: QA activity, where the tester tries to understand what happened to the bug has found in production
• Postponed: The team lead or product decides that bug doesn’t have sufficient priority to be fix right now.
• Deferred: The defect isn’t a defect or is duplicated.
• Regression: Normally, it is when you fix a bug and the bug returns.