All About bout Defect Triage
Posted By : Aarushi Sharma | 25-Dec-2017
Defect Triage is used to prioritize a bug based on its severity, priority, risk etc.
Why is Defect Triage needed?
1.Defect Triage is used to prioritize, evaluate and check the solution of the defect.
2.These meetings are done to analyze defects and described an action to be taken on these defects.
3.This involves assigning and rejecting defects created from he last meeting.
How Defect Triage needs to be conducted in a release?
The Defect Triage meeting is not fixed.It changes from project to project.
Important factors of a meeting are:
1.Depend upon Project Schedule.
2.Number of bugs
3.Team member availability
Participants of Defect Triage:
Mandatory Participants:
1.Project Manager
2.Test Team Lead
3.Development Team Lead
Other Participants:
1.Developer
2.Tester
3.B.A
Test Team Leader
1.Schedule triage meeting and send the meeting notification to attendees.
2.Creating defect report and send to all attendees.
3.Give priority and severity to the defects.
4.Explain root cause to other team members.
5.Create the notes of the meeting and send it to the attendees.
Development Lead
1.It explains the prioritization of the defects.
2.Explains the risk involved in the defect.
3.Assign defects to the developer.
Project Manager
1.It also helps in a prioritization of defects.
2.Discussion on next release date.
What happens during Defect Triage Meeting?
1.Testing lead creates a bug report.During the meeting, each defect is analyzed whether right priority is assigned to the defects.
2.Priorities can be changed if needed.
3.A defect is analyzed on the basis of there severity.
4.Any update regarding the defects is captured in bug tracking system.
5.Comments field should be updated by noting essentials points of the meeting.
Defect Triage Template:
1.Id of the defect
2.Description
3.Date on which the report is created
4.Name of the Reporter
5.Severity of the bug
6.Priority
7.Status of the bug
An outcome of the Defect Triage meeting?
Defect Triage Metrics will be prepared at the end of every meeting and given to all attendees.This report will help for the future meetings.
Thanks
Cookies are important to the proper functioning of a site. To improve your experience, we use cookies to remember log-in details and provide secure log-in, collect statistics to optimize site functionality, and deliver content tailored to your interests. Click Agree and Proceed to accept cookies and go directly to the site or click on View Cookie Settings to see detailed descriptions of the types of cookies and choose whether to accept certain cookies while on the site.
About Author
Aarushi Sharma
Aarushi is a bright QA engineer with experience in manual testing. Apart from that she loves to dance.