Entries Tagged 'Bug Defect tracking' ↓

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 →




How to Prepare Yourself For Test Case Writing and Improve Your Productivity

When a tester decides to write high quality test cases and wants to improve their efficiency and the productivity of test case writing, there are few key points which help the testers to achieve these goals.

First, they need to prepare themselves professionally and psychologically with some of the key points necessary for every successful software testers in the IT industry. This will be treated as “Inputs” for a tester before starting to write test cases. Continue reading →

Why Bug Reporting is an Art That Should Be Learned by Every Tester?

What exactly the tester is supposed to do? I was just brainstorming with my team. Number of answers popped up:

  • Should test
  • Should test thoroughly
  • Should not miss any bug
  • Should understand application
  • Should try to break the application

Continue reading →

Important Software Test Metrics and Measurements – Explained with Examples and Graphs

In software projects, it is most important to measure the quality, cost and effectiveness of the project and the processes. Without measuring these, project can’t be completed successfully.

In today’s article we will learn with examples and graphsSoftware test metrics and measurements and how to use these in software testing process.

There is a famous statement: “We can’t control things which we can’t measure”.

Here controlling the projects means, how a project manager/lead can identify the deviations from the test plan ASAP in order to react in the Continue reading →