Quality Testing

Quality is delighting customers

How to report a bug?

please give me a simple example to report a bug

 

Thanks in advance,

sanu r

Views: 7035

Reply to This

Replies to This Discussion

 

Hi Sanu,

 

Simple example to report a bug:

 

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

 

1)Summary           :  Here Mention Summary of your bug (for example: Login Button is not working)

 

2)Status               : Here mention the status of your bug (for example: Open (If new bug))

 

3)Issue Type        : Mention type of Issue (for example whether it is a enhancement or etc.)

 

4)Application      : Here Mention your application name

 

5)Version found  : Here Mention your Application version

 

6)Module Name   : Here Mention module name in which u found a bug

 

7)sub-Module      : Here mention sub Module name if any

 

8)Severity           : Its depend  of your project

 

9)Priority            : Its depend on your project

 

10)Environment   : Here mention the testing environment in which u tested. (for example: Window XP,

                              Brower: IE8.0, etc.....)

 

11)Step to reproduce:

     .......

     .......

   Occurance  n/n

 Mention occurance also ( Is nothing but how many time u tried and how many time u able to reproduce the bug)

  

 And dont forget to attached the screen shotAttached the screen shot

 if u r using Ms-Excel to report the bug then mention the Bug Raised date also, if any using any tool then no need.

 

 

With Warm Regards,

Faroz

 

hey thanks firoz

 

Always welcome Yaar

Hi Sanu, Please find the attached excel file for bug reporting sample. Hope that works for you.

Thanks

Hanee Srivastava

Attachments:

thanks hanee

 

 

Your welcome ma'm!!

 Hi Sanu,

  Please find the attached excel file for bug reporting sample. Hope that works for you.

 

 Thanks

 Sandip Wagh

(9923453129)

 

Attachments:
please check test cases of login and registration page and if is there any correction please reply.
Attachments:

hi sagar,

firstly please tell me alld req for this

for password and user name

thanks

 

Hello,

I hope you are doing good...

There are lots of things which you need to keep in mind before creating a bugs report ..

please check here:https://www.testrigtechnologies.com/how-to-write-a-better-bug-report/

Hello,

I hope you are doing good...

There are lots of things which you need to keep in mind before creating a bugs report ..

please check here: How to write a Better Bug Report

As per best practice of Software testing solutions, below is the sample of bug report.

Bug Report: It represents the list of bugs encountered by tester while testing a software product. Bugs/defects report are the most effective way for developers to understand where the product is lacking its functionality or performance.

What is a Useful Bug Report:
1: Pinpoint the bug
2. Explain it to the developer.

Bug reporting Guidelines:
1. Avoid duplicates: Search before you file.
2. Always test on latest available build.
3. State useful facts, not opinions or complaints.

How to Write a Good Bug Report:
A good bug report  should include the following information:

1. Summary : It is read more often than any other part of the bug. It says all about what comes in the bug. The goal of summary is make the issue searchable and uniquely identifiable.
A bad example : Application crashes
A Good example :Application stops responding when user clicks on 'User details' button under menu drop down.

2. Prerequisite: A thing that is required on priority basis for something else to happen.
Example : User should have connected to XYZ vpn to access the ABC application.

3. Steps to Reproduce: The goal of reproducible steps is to teach developer to recreate the bug on his/her own system. Minimized, easy-to-follow steps that will trigger the bug.

 A good example of this would look like the following:

1) Access the ABC application in Chrome browser.
2) Log into the application with valid credentials.
3) Click on Menu button displayed in the right panel.
4) Now redirect to Menu  and clicks on User details button.
5) Now observe once user click on User details button application stops responding.

4. Expected and Actual Results :Expected Result and Actual Result, will show the developer what's wrong. Expected Result describes what should have happened, and Actual Result describes what actually is happening.

Example is as follows:
Actual Result : Application stops responding when user clicks on 'User details' button under menu drop down.
Expected Result: Application should not stop responding once user clicks on 'User details' button under menu drop down.

5. Screenshot/Video:
Take a Screenshot of the instance of failure with proper captioning to highlight the defect. Highlight unexpected error messages with light red color which draws attention to the required area.

6. Priority
Based on the severity of the bug, a priority can be set for it. A bug can be a Blocker, Critical, Major, Minor, Trivial, or a suggestion.
A bug priority from P1 to P5 can be given so that the important ones are viewed first.


Status: Whether it’s a new bug, fixed, verified, etc

7. Testing details :
Tested with user: ****
Tested on Browser [Platform/Environment]: Chrome , Firefox, IE
Build Number: ****
Screen resolution :
Environment : UAT/QA/STAGE
URL: URL of the page where the actual bugs occur.

Thanks

RSS

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2019   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service