Entries Tagged 'Bug Defect tracking' ↓

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 →




How to Reproduce a Non-Reproducible Defect and Make Your Testing Effort Worth It

In the world of software testing a defect once found should be consistently reproducible so the tester can report with conviction, developer can fix with clarity and the QA team can close with confidence.

However, this process sometimes comes with its own set of challenges. This article tries to illuminate those dark areas of defect reproduction.

First of all, what is “Reproducing a Defect”? Continue reading →

Getting Started with Incident Tracking and Management in Software Testing (Sample Templates Included)

In today’s article we are going to learn all about the “Incident Tracking and management” Process – How to track and manage incidents in Software Testing with sample templates.

Are you thinking- “STH has published a lot of content on defect/bug tracking, so how is this going to be different”? That is exactly the reason why we have to look at what we mean by incident first. Continue reading →

The Art of Bug Reporting: How to Market and Get Your Bugs Fixed?

Why there is a need for Marketing a Bug?

The first things that come to my mind as I start writing this article are the words of Cem Kaner“The best tester isn’t the one who finds the most bugs or who embarrasses most programmers. The best tester is the one who gets most bugs fixed.”

Now – What is the difference between finding most bugs and getting most bugs fixed?

Isn’t it obvious that any bug logged in a bug management system should be fixed by the developers? The answer is No. Factors like time to market the product, time to complete project on schedule and developers working in Continue reading →