Entries Tagged 'Bug Defect tracking' ↓

3 Worst Defect Reporting Habits and How to Break Them

Defects are serious business and small mistakes can be expensive.

You know what to do when you find a defect. You report it; either in a Defect Tracker/Defect Management tool or in an Excel sheet. The underlying principles are the same for both methods.

Defect Management tools don’t guarantee better reporting. It is good practices that save the day. Continue reading →

How Do You Decide Which Defects are Acceptable for the Software to Go-live?

Software Go-Live is always a big event for any software product. It is important to absolutely make sure that everything works and that we are releasing quality software to the users.

A bad or premature or unstable or difficult to use product can cause a lot of losses financially and could also make the user lose trust in the brand itself.

------------

Often times, we hear that testing should be done until we meet the exit criteria. We also hear that defects have to be fixed to an acceptable level.  Continue reading →

A Step by Step Guide to IBM Rational ClearQuest Tool

For each and every project, as per the Client’s requirement and ease, various tools are recommended and used.

For example, few projects prefer ‘Quality Center’ for managing the project’s data whereas few others prefer Rational ClearQuest tool.

Rational ClearQuest is a defect management and workflow automation software from IBM Rational software division.  Continue reading →




7 Types of Software Errors That Every Tester Should Know

It’s time again for a post on software testing basics. This post is on types of software errors that every testers should know.

Software bugs are of many types. A bug is a bug no matter what. But sometimes, it is important to understand the nature, its implications and the cause to process it better.

This helps for faster reaction and most importantly, appropriate reaction.

In this article, we will be discussing common kinds of software errors and how to identify them during testing with some examples and simple exercises.

Let us start by defining software error and bugs. Continue reading →

This Scenario Explains How Important It is to Document the Frequently Encountered Errors

Do you believe that software errors occur only once and that on being fixed they never resurface? I feel that about 30% of the errors reoccur.

In this article, I want to cover how important it is to document some of the frequently encountered errors.

Below, you will find some common areas where issues are seen and a template to document them.  Continue reading →

3 Strategies for Dealing with a Blocker Defect

Blocker defects add tons of drama to otherwise regular test days.

In this article, I want to cover some steps a tester can take when dealing with them.

I am going to assume that our dear readers already understand Severity and Priority of defects deeply. Need a quick recap? Check this out.

Now, does it always mean we need to completely stop testing if we come across a blocker issue?  Continue reading →