Entries Tagged 'Bug Defect tracking' ↓

How to Set Defect Priority and Severity (with Defect Triage Process)

In this tutorial you will learn what is Defect Priority, What is Defect Severity, How to set it, and Defect Triage process with many examples to understand the concept clearly.

Introduction

Filing defects is a very integral part of the Software Testing Life Cycle. There are several best practices defined for effective defect reporting over the internet or in organizations. One of the important aspects of the defect life cycle on a generic level includes defect Continue reading →

Cosmetic and the Functional Bugs – What has to be Treated and How?

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.

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

cosmetic bugs vs functional bugs

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 →

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 team mate was fuming and the discussion suddenly caught fire when couple of other team mates joined in sharing 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 behavior during exploratory testing.

What happens when we encounter these deviations?

Continue reading →

15 Most Popular Bug Tracking Software to Ease Your Defect Management Process

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 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 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 logon 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”.

But when you entered into your application by logging in and navigated to USERS menu > New user, entered all the required information to create new user and clicked on SAVE button. BANG! The application crashed and you got one error page on screen. (Capture this error message window and save as a Microsoft paint file)

Now this is the bug scenario and you would like to report this as a BUG in your bug-tracking tool.

How will you report this bug effectively?

Here is the sample bug report for above mentioned example:
(Note that some ‘bug report’ fields might differ depending on your bug tracking system)

SAMPLE BUG REPORT:

Bug Name: Application crash on clicking the SAVE button while creating a new user.
Bug ID: (It will be automatically created by the BUG Tracking tool once you save this bug)
Area Path: USERS menu > New Users
Build Number: Version Number 5.0.1
Severity: HIGH (High/Medium/Low) or 1
Priority: HIGH (High/Medium/Low) or 1
Assigned to: Developer-X
Reported By: Your Name
Reported On: Date
Reason: Defect
Status: New/Open/Active (Depends on the Tool you are using)
Environment: Windows 2003/SQL Server 2005

Description:
Application crash on clicking the SAVE button while creating a new
user, hence unable to create a new user in the application.

Steps To Reproduce:
1) Logon into the application
2) Navigate to the Users Menu > New User
3) Filled all the user information fields
4) Clicked on ‘Save’ button
5) Seen an error page “ORA1090 Exception: Insert values Error…”
6) See the attached logs for more information (Attach more logs related to bug..IF any)
7) And also see the attached screenshot of the error page.

Expected result: On clicking SAVE button, should be prompted to a success message “New User has been created successfully”.

(Attach ‘application crash’ screen shot.. IF any)

Save the defect/bug in the BUG TRACKING TOOL.  You will get a bug id, which you can use for further bug reference.
Default ‘New bug’ mail will go to respective developer and the default module owner (Team leader or manager) for further action.

Related: If you need more information about writing a good bug report read our previous post “How to write a good bug report“.