Defects or Bugs In Software Testing

When you speak about Software Testing, bugs or defects form an integral part. Basically, the intention of Software Testing or QA Testing is to find the defects in the software, to deliver a quality product in the end. In today’s times, quality is one thing high on the priority list of customers and clients. This applies to the software field as well. Therefore, finding out bugs and fixing them forms an integral part of this field.

Definition of defects or bugs:

A defect is simply an error or a bug found in the software. It is an evidence kind of a thing, which suggests that the software is not working as expected. We are not getting the desired output.

In short, when the actual result does not match the expected result, then the outcome is a defect.

What are the causes of errors/bugs ?

A developer, while developing a particular application or a software is bound to make mistakes. They may be because of human errors or other factors like syntactical or coding time errors.

If the client requirements are not understood correctly, it may lead to functionality related defects. In this case, the functionality of the application may not match with the client’s requirements.

All these things mean that there are flaws in the software. These are termed as defects.

Therefore, anything which does not match with the requirements stated in the SRS document, is termed as a bug or a defect. Bugs or defects result into unexpected results which hamper the quality of your product.

More Information on Bugs:

  • If a large number of bugs or defects are found in a software application, then it is often called as “Buggy”.

  • Whenever a software tester discovers a bug in the application, he needs to report it to the developers for fixing. The testers report the bugs by filing them in bug tracking tools like Bugzilla. In that, they describe the bug in detail and assign it to the developers for fixing.

The various fields present in the Bug tracking tools are as follows:

  • Defect ID:

Each bug filed has a unique identification number or defect ID which is helpful while tracking a bug.

  • Defect Description:

This field consists of the summary of the bug.

  • Product Version:

The version of the software application in which the defect is found is mentioned in this field.

  • Detail Steps:

This field is important as it contains the bug description in detail along with the steps to reproduce the bug. Snapshots are also attached if required. After reading this, the developers get a clear idea about the defect.

  • Date:

The date on which the bug was raised, is mentioned here.

  • Reported By:

The details of the tester who filed the bug are mentioned here.

  • Status:

Describes the status of the bug as in new, assigned, open, fixed, reopened, closed etc. These may vary a little as per the requirement of the organization.

  • Fixed By:

Details of the developer who fixed the particular bug are mentioned in this field.

  • Date Closed:

The date on which the bug was fixed and closed.

  • Severity:

This is an important field while filing a bug, and mentions the impact of the bug on the software under question. Generally, the severity is categorized into types like Critical, Major and Minor. This is based on the amount of impact it would leave on the application.

  • Priority:

After seeing the priority level, the developer can decide the urgency level of fixing the bug. Priority can be set as either High, Medium or Low as per the need.

This was an outline regarding “defects” in software testing.

More Related Video:

Integration Testing Overview

This article would be helpful for Student Software Testing Reviews.

Leave a Reply

Your email address will not be published. Required fields are marked *