Scribd
Upload
12 views

STE Unit 4

Uploaded by

Shubham Ingale
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
12 views

STE Unit 4

Uploaded by

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

Software Testing UNIT 04

4.1 4.2

Defect Classification Defect Life Cycle

Based of Severity

1. Minor
2. Major
3. Critical
4. Trivial

Based on Impact

1. Security
2. Functional
3. Non Functional
4. Compatibility
Defect Report
Defect Management Process

1. Detect: Bugs pop up during


development. Testers, users, even
robots can spot them.

2. Report: Log the bug in a central


system, like a defect management
system (DMS), with details like how to
recreate it and how bad it is.

3. Analyze & Prioritize: Developers


investigate and rank the bug based on
its impact - critical crash vs. minor
typo, you know the drill.

4. Fix: Developers get to work,


4.3
debugging code and testing the fix.
Estimate Expected Impact of Defect
5. Verify & Close: Testers confirm the
bug is gone, and it's officially banished! Estimation of Impact includes:

6. Improve: Learn from past bug 1. Severity: How bad is it (crash? data
outbreaks to prevent future ones. loss? typo?)
2. Likelihood: How often does it happen
(always? rarely?)
3. Scope: How much does it affect (whole
system? one feature?)
4. Consequences: What's the potential
damage (money? reputation?)
5. Risk Matrix: Combine severity &
likelihood for fix priority.
Techniques to find defects
Static Techniques:
Software Testing UNIT 04

• Code Reviews: Experts manually


analyze code for errors.
• Static Code Analysis: Tools
automatically scan code for
vulnerabilities.
• Requirements Reviews: Checking
requirements documents for
inconsistencies.
Dynamic Techniques:
• Unit Testing: Testing individual units of
code in isolation.
• Integration Testing: Testing how
multiple units of code work together.
• Functional Testing: Checking if the
software behaves as expected.
• Non-Functional Testing: Evaluating
performance, security, and usability.
• Exploratory Testing: Ad-hoc testing to
discover unexpected issues.
Reporting of Defect
Effective defect reporting involves capturing
the who, what, when, where, and why of the
issue:
• Who discovered the defect?
• What is the specific problem
observed?
• When and under what conditions did it
occur?
• Where in the system or functionality
does it happen?
• Why is it a problem and what's the
potential impact?
Clear, concise reports with detailed steps to
reproduce the defect enable developers to
quickly fix it. Remember to include
screenshots, logs, or relevant data when
feasible.

You might also like