Entries Tagged 'Bug Defect tracking' ↓

10 Reasons Why Your Bugs are Getting Rejected and What You Can Do for it as a Tester!

I am not going to spare her. She has rejected 7 bugs, I reported, within last three days. I know she is using personal grudges as professional sword……

A teammate was fuming and the discussion suddenly caught fire when a couple of other teammates joined in sharing the same experience with other developers. The team meeting turned a discussion point about bug rejection. After some discussion, we all decided to do a simple exercise to save ourselves from the humiliation of bug rejected, in future.

Continue reading →

Live Project Bug Tracking, Test Metrics, and Test Sign off – Free QA Training Day 6

This is the concluding part of our “software testing training on a live project” series.

It is going to be about defects and also few remaining topics that will mark the completion of Test execution phase of the STLC.

In the previous article, while Test Execution was going on, we encountered a situation where the expected result of test case was not met. Also, we identified some unexpected behaviour during exploratory testing.

What happens when we encounter these deviations?

Continue reading →

15 Best Bug Tracking Software: Top Defect/Issue Tracking Tools of 2018

We are testers – in other words, bug finders. Defect/ Bug/ Issue/ Fault/ Failure/ Incident – whatever we choose to call – our primary job description revolves around finding, recording, reporting, managing and tracking these.

While there is no harm in using an excel sheet to record/track and emails to report/ alert/ communicate – as the magnitude of the projects, the number of test cycles, the count of the people involved grows – it becomes absolutely important that we need a much stronger mechanism that will make the management of these issues simpler and consistent so we can concentrate harder on actually finding more issues in the AUT than managing the ones already found.  Continue reading →

Sample bug report

This is the guest post from Vijay D (Coincidence with my name).

Below sample bug/defect report will give you an exact idea of how to report a bug in bug tracking tool.

Here is the example scenario that caused a bug:

Lets assume in your application under test you want to create a new user with user information, for that you need to login into the application and navigate to USERS menu > New User, then enter all the details in the ‘User form’ like, First Name, Last Name, Age, Address, Phone etc. Once you enter all these information, you need to click on ‘SAVE’ button in order to save the user. Now you can see a success message saying, “New User has been created successfully”.

Continue reading →

How to get your all bugs resolved without any ‘Invalid bug’ label?

I hate “Invalid bug” label from developers for the bugs reported by me, do you? I think every tester should try to get his/her 100% bugs resolved. This requires bug reporting skill. See my 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 bug being marked as invalid is “Insufficient troubleshooting” by tester before reporting the bug. In this post I will focus only on troubleshooting to find main cause of the bug. Troubleshooting will help you to decide whether the ambiguity you found in your application under test is really a bug or any test setup mistake.

Continue reading →

How to Write a Good Bug Report? Tips and Tricks

Why good Bug report?

If your bug report is effective, then its chances to get fixed are higher. So fixing a bug depends upon how effectively you report it. Reporting a bug is nothing but a skill and I will explain how to achieve this skill.

“The point of writing problem report(bug report) is to get bugs fixed” – By Cem Kaner. If a tester is not reporting a bug correctly, the programmer will most likely reject this bug stating it as irreproducible.  Continue reading →

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

Introduction to Defect Life Cycle:

In this tutorial, I 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.

I have also added the most frequently asked interview questions on defect life cycle. This is important to know about the various states of a defect for understanding the life cycle of a defect. The main intention of performing a testing activity is to check if the product has any issues/errors. Continue reading →

How to write software Testing Weekly Status Report

Writing 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?

Here I am going to give some tips. The weekly report is important to track the important project issues, accomplishments of the projects, pending work and milestone analysis. Even using these reports you can track the team performance to some extent. From this report prepare future actionable items according to the priorities and make the list of next weeks actionable.

Continue reading →

How to find a bug in application? Tips and Tricks

A very good and important point. Right? If you are a software tester or a QA engineer then you must be thinking every minute to find a bug in an application. And you should be!

I think finding a blocker bug like any system crash is often rewarding! No I don’t think like that. You should try to find out the bugs that are most difficult to find and those always misleads users.

Continue reading →

Bugzilla Tutorial: Defect Management Tool Hands-on Tutorial

Bugzilla is an open-source Bug tracking tool. Many companies are using this open source tool for managing the software development process.

Bugzilla is defect/bug tracking tool. Defect tracking systems allow developers and testers to track all the outstanding defects. Bugzilla can be linked to other testing tools like JIRA, QC or ALM etc. Bugzilla is developed in Perl and runs on MYSQL server.  Continue reading →