Bug Defect tracking

What is defect and how to track it? Detailed bug/defect tracking process with defect life cycle, bug logging process with sample defect reports etc. Find list of best defect tracking software as well.

Sample Bug Report: Format, Template and Examples (UPDATED)

Sample-bug-report

This tutorial explains the Sample Bug Report Template field with examples and explanations to give you an exact idea of how to report a Bug:

If all building/development practices result in perfect systems and solutions, there is nothing left to question and validate. However, that is rarely true. Many things go wrong to various degrees and that warrants thorough verification and validation testing to ensure things are in order.

Enter systematic software testing and bug/defect reporting. Bug or Defect reports are part and parcel of a tester’s day-to-day life. We create defects, assign defects, retest fixed defects, find defect root causes, categorize defects per functionality, reference defects in our conversations, etc.

So, it is understandably a very important part of a tester’s job profile.

Read more


How to get all your Bugs resolved without any ‘Invalid Bug’ label?

HOW TO GET YOUR ALL BUGS RESOLVED WITHOUT ANY 'INVALID BUG' LABEL_

Do we all hate the “Invalid bug” label from our developers for the bugs reported by us? I think every tester should try to get his/her 100% bugs resolved. This requires bug reporting skills.

Take a look at our previous post on “How to write a good Bug Report? Tips and Tricks” to report bugs professionally and without any ambiguity.

The main reason for the bug being marked as invalid is due to “insufficient troubleshooting” by the tester before reporting the bug.

Read more


How to Write a Good Bug Report? Tips and Tricks

How To Write A Good Bug Report

Here’s how to write a good bug report with some helpful tips and tricks. Let’s get started.

“The point of writing a problem report (bug report) is to get bugs fixed” – Cem Kaner.

If a tester is not reporting a bug correctly, then the programmer will most likely reject it stating it as irreproducible. This can hurt the tester’s morals and sometimes ego as well.

If the Bug report is effective, then its chances of getting fixed are higher. So fixing a bug depends upon how effectively you report it. Reporting a bug is nothing but a skill and in this tutorial, we will explain how to achieve this skill.

Read more


What is Defect/Bug Life Cycle in Software Testing? Defect Life Cycle Tutorial

Defect Life Cycle Tutorial

Introduction to the Defect Life Cycle

In this tutorial, we will talk about the life cycle of a defect to make you aware of the various stages of a defect which a tester has to deal with while working in a testing environment.

We have also added the most frequently asked interview questions on Defect Life Cycle. It is important to know about the various states of a defect in order to understand the life cycle of a defect. The main intention of performing a testing activity is to check if the product has any issues/errors.

Read more


How to Write Software Testing Weekly Status Report

Software Testing Weekly Status Report

Writing an Effective Status Report is as important as the actual work you did! How to write an effective status report of your Weekly Work at the end of each week?

This tutorial will offer you some tips on this. A weekly report is important to track the important project issues, accomplishments of the projects, pending work, and Milestone Analysis.

Using these Reports, you can even track the team’s performance to some extent. From this Report, you can prepare future actionable items according to the priorities and make a list of the next week’s actionable.

Read more


How to Find a Bug in Application? Tips and Tricks

How to Find a Bug in Application

Here you will find some useful suggestions and guidance on How to Find a Bug in Application. Also, understand the different approaches to defect discovery:

Testing is often simplified as a bug-finding activity. Even though that’s not the entire job profile of testers, finding problems before the end users do is the long and short of our core duties. So, should testers worry when they test software and find no defects?

In other words, do zero defects mean no testing occurred? Not true. All testing finds defects. All software has bugs. It is up to the tester’s skill, time available, background information provided, domain knowledge, resources allocated, etc. that influences the question – How to find defects in an application?

It is hard to quantify how to develop the skill of finding defects but be assured that testers get especially better with experience and exposure to various kinds of software systems and their functionality.

Read more