In the world of software testing, a defect once found should be consistently reproducible so the tester can report with conviction, a 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.
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 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.”
Isn’t it obvious that any bug logged in a bug management system should be fixed by the developer? The answer is No. Factors like time to market the product, time to complete the project on schedule and developers working in Continue reading →
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 →
In this tutorial, you will learn what is Defect Severity and Priority in testing, how to set defect priority and severity levels with examples to understand the concept clearly.
We will also cover in detail on how to classify the defects under different buckets and their relevance in defect life cycle. We will also cover the crucial role of the classification with the live set of examples. Continue reading →
There are always huge responsibilities imposed on the tester to uncover any kind of bug that software has got. Irrespective of the functionality and user interface, testers can raise bugs wherever there is a non-conformance.
This article helps in understanding the importance of the functional and the cosmetic bugs. Additionally, the factors to be considered in prioritizing them are also explained here in an understandable way with some live examples for illustrations.
Bugs are inevitable in the Software development. Hence it is always very important to perform the software a through testing before it can be Continue reading →