Scribd
Upload
4 views16 pages

Defect Management

Defect management is a structured process used by QA teams to identify, log, prioritize, resolve, and track software defects throughout the development lifecycle. Key steps include defect identification, logging, triage, assignment, resolution, retesting, and closure, utilizing tools like Jira and Bugzilla. Best practices involve detailed reporting, regular triage meetings, and effective communication among team members to maintain software quality and reliability.

Uploaded by

hari36066
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
4 views16 pages

Defect Management

Defect management is a structured process used by QA teams to identify, log, prioritize, resolve, and track software defects throughout the development lifecycle. Key steps include defect identification, logging, triage, assignment, resolution, retesting, and closure, utilizing tools like Jira and Bugzilla. Best practices involve detailed reporting, regular triage meetings, and effective communication among team members to maintain software quality and reliability.

Uploaded by

hari36066
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

DEFECT

MANAGEMENT
Defect
Management
Defect management is the structured
process used by QA teams to handle bugs
and issues discovered during testing. It
ensures that all defects are properly
recorded, analyzed, prioritized, resolved,
and tracked to closure.

Defect Management in QA is a critical


process that ensures software quality by
identifying, tracking, resolving, and
preventing defects throughout the software
development lifecycle.
Steps in the Defect Management
Process
• Defect Identifi cation
Defects are discovered during testing or use.
Reported by QA, users, or automated tools.
• Defect Logging
Logged into a defect tracking system (e.g., Jira).
Includes details like title, description, steps to reproduce,
severity, priority, screenshots, etc.
• Defect Triage
Team (QA, Dev, PM) reviews and prioritizes defects.
Decides urgency (priority) and impact (severity).
Steps in the Defect Management
Process
• Defect Assignment
Assigned to a developer or team for resolution.
• Defect Resolution
Developer fi xes the bug and updates the status.
• Retesting
QA tests the fi xed issue to confi rm resolution.
• Closure
If the defect is resolved and verifi ed, it is closed.
If not fi xed properly, it is reopened.
Defect Tracking Tools

Popular
tools used:
• Jira
• Bugzilla
• Azure
DevOps
• eTraxis
Defect Management Tools
Overview

• Jira - Highly customizable, integrates with


CI/CD
• Bugzilla - Open-source, detailed defect
tracking
• Azure DevOps - Integration with DevOps
pipelines
• eTraxis - Fully customizable, open source
Types of Defects in QA

• Functional Defects: These are probably what come to mind fi rst.


They mean the software isn't doing what it's supposed to do.
Think a button that doesn't work, a calculation that's wrong, or
a feature that's missing.
• Usability Defects: These issues make the software diffi cult or
frustrating to use. Maybe the navigation is confusing, the layout
is messy, or the error messages are unhelpful. It might
technically work, but it's not a pleasant experience.
• Performance Defects: These relate to how well the software
performs under diff erent conditions. Slow loading times,
crashes under heavy load, or excessive resource consumption
fall into this category.
Types of Defects in QA

• Security Defects: These are critical as they can expose


vulnerabilities in the software, allowing unauthorized access or
data breaches. Think weak passwords, SQL injection fl aws, or
lack of encryption.
• Compatibility Defects: These arise when the software doesn't
work as expected across diff erent environments – diff erent
operating systems, browsers, devices, or even other software.
• Error Handling Defects: These occur when the software doesn't
gracefully handle errors or unexpected situations. Instead of
providing informative messages or recovery options, it might
crash or display cryptic errors.
Defect Status Workflow

• New – Logged and awaiting triage.


• Open – Accepted as a valid issue.
• Assigned – Developer is working on it.
• Fixed – Developer marks it as resolved.
• Retest – QA verifi es the fi x.
• Closed – Verifi ed as fi xed.
• Reopened – QA fi nds it's still present or not fi xed properly.
• Deferred – Postponed for a future release.
• Rejected – Not considered a defect or not reproducible.
Severity and Priority Matrix in QA

• The Severity and Priority Matrix is a tool used in software


testing and quality assurance to classify and manage defects
(bugs) based on:
• Severity – How serious the defect is.
• Priority – How urgently the defect should be fi xed.
• Together, these two help teams triage defects eff ectively and
allocate resources smartly.
Best Practices for Defect
Management
• Provide detailed, reproducible defect reports.
• Use standardized severity and priority levels.
• Conduct regular defect triage meetings.
• Maintain traceability between requirements, test
cases, and defects.
• Encourage open communication between QA, Dev,
and stakeholders.
• Automate tracking and reporting wherever
possible.
Defect Prevention Strategies

• Thorough requirement analysis


• Code reviews and peer testing
• Test automation for regression
• Continuous Integration/Continuous Deployment
(CI/CD)
• Maintain a knowledge base of past defects and fi xes
Goals of Defect Management

• Maintain software quality and reliability


• Ensure effi cient bug resolution
• Track and report defect-related metrics
• Enable better team collaboration
• Reduce defect leakage to production
Thank you
very much!

You might also like