All about Bug or Issues

All about Bug, Error and Defects

Error: Mistake in code is error. Error is an undesirable deviation from requirement

Bug: if defect accepted by the development team it is called bug. Bug is an error found before the application goes into production

Defect: Defect is a variance from desired product attributes or normal flow. When defect reaches to end customer is termed as failure. Defect is an error found after the application goes into production.

Defects can be from product specification

Defects can be from customer or user expectation.

Attributes of Defect

1. Defect Naming – requirement defect, design defect, documentation defect

2. Severity of Defect

• Critical (high) –show stopper
• Major (high) incorrect output derived
• Minor (Low) spelling mistake

3. Type of Defect

• Wrong- requirements implemented incorrectly
• Missing – requirement given by end customer but it were not implemented at all
• Extra – requirement implemented correctly but were not requested by end customer

About Severity and Priority

Severity: Seriousness of defect with respect to functionality

Priority: importance of defects with respect to customer

• · High: without resolving defect we are unable to continue testing
• · Medium: compulsory to solve but able to continue
• · Low: may or may not be resolved

Examples:

• User interface bug- low severity
• Calculation bug- high severity and high priority bug
• Improper alignment – low priority and low severity bug
• Spell mistake – high priority and low severity bug
• Final output wrong – low priority
• Dependent output wrong – high priority
• Annual report print functionality not working – High severity and low priority issue

Components of Bug

• Title of bug
• Severity of bug
• Priority of bug
• Bug type
• Module name
• Assigned to
• Project manager
• Steps to reproduce
• Actual output
• Expected output
• Attachment of log and screen shot
• Comments
• Test environment – browser, OS information etc
• Build date and platform

Guidelines to write bug

• Be precise
• Be clear – explain it so other can reproduce the bug
• Mention exact steps to reproduce with details
• Provide sufficient test environment details
• Mention build date and number with details
• When you close your bug mention on which build and date you verify it, so in future if require to reopen it we can have track on which build it works last

Defect Density

defect density is the count of total defects identified against a particular software entity it is calculated as... no of defects/ size of software where size is typically counted in lines of code this is used to compare the relative number of defects in various software components, to find out the defect prone areas of the application

Defect density = Total number of defects/LOC (lines of code)

Defect density = Total number of defects/Size of the project Size of Project can be Function points, feature points, use cases, KLOC etc