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“.



Get FREE eBook + Blog Updates By Email!

Subscribe to get software testing awesome articles and free resources. Enter your email address and click 'SIGN UP NOW' button.


146 comments ↓

#1 shabina on 05.04.08 at 6:17 am

Hi Vijay,
This is reporing of very simple bug. But nice and easy to understand….

THANX……

#2 W@leed on 05.04.08 at 6:24 am

Well this is nice effort done by Vijay. It’s simple & easily understandable Bug Report.
Can you pls write for BUG Tracking tool like wise Bugzilla, Matins i mean the complete installation about these Bug Tools.

#3 navin bhalla on 05.05.08 at 4:39 am

see there is always said for the making of the GUI.Could u please tell me briefly about it.

#4 Simran on 05.05.08 at 5:39 am

thanks for providing such a simple and useful bug report.
your article on how to write a good bug report is also very informative and useful.

#5 R.N.Muni on 05.05.08 at 5:57 am

Hi,
vijay the bug report is very easy to under stand and it is very useful
I want some infermation please tell me,what is difference between QC and Test Director.

#6 Abhishek on 05.05.08 at 7:58 am

HI vijay

Nice effort by u.

Thanks

#7 Yogesh Dhage on 05.05.08 at 9:04 am

Simple and easily understand bug report and very useful

#8 Ashima on 05.05.08 at 10:14 am

hi vijay.

The report is of great help for begginers like me. it’s easy to understand. Thanks. Keep providing such help.

#9 Jack on 05.05.08 at 11:31 am

Good explanation.Easy to understand.

#10 Anil kumar (Swapnil) on 05.05.08 at 11:42 am

Hiiiii
I’m Anil
Is available any tool for crash any web page?
And pls tell me about DB testing…..
Thanksss

#11 vimal on 05.05.08 at 3:43 pm

hai vijay,

Thanks for ur information. It was short & informative. Can you plz tell me what all are the status having in QC? And who and all are been assigned to?

#12 visu on 05.06.08 at 7:05 am

hello vijay..
very good we r pleasure to read.thanks

#13 Nizam on 05.07.08 at 4:26 am

try to give a more complex scenario

#14 vamsi on 05.08.08 at 5:26 am

Its very simple and easy to understand

Thanks

#15 ngocvk on 05.08.08 at 7:15 am

It’s very useful with me. Thanks Vijay

#16 Mahalakshmi on 05.08.08 at 9:18 am

Hi Vijay, Really thanks to say u for ur helpsssss…………

I can understand this and getting easily. could u please send me bug report and defect track and what are all include in testing. if u possible to mail me means really saying thanks……………

#17 VijayD on 05.08.08 at 9:24 am

@Mahalakshmi,

Please provide the email ID.

Regards,
VijayD

#18 Basu on 05.08.08 at 9:41 am

This site is very usefull.Its very simple and easy to understand

#19 Dipali on 05.09.08 at 7:23 am

Hi vijay
its very simple to understand will u give details of Bugzilla installation

#20 parag on 05.09.08 at 9:49 am

very nice bug report

#21 Chandru on 05.12.08 at 12:48 pm

Very nice ! Thanks for the report !

#22 Jai on 05.14.08 at 7:01 am

Who sets the severity and priority for the bug?

#23 vinoth on 05.14.08 at 7:24 am

Please anyone give idea , how can i get free demo version of QTP (or ) Winrunner.

#24 saikala on 05.14.08 at 7:35 am

hi

#25 Reema Karande on 05.17.08 at 11:19 am

hi all ,
i just want to know about the situation with the help of an example : where there are
high Severity&high priority bugs
high Severity & low priority bugs
High priority & low severity bugs
low priority & low severity bugs

#26 Vijaya Kawadkar on 05.17.08 at 11:57 am

High Priority & Low Severity Bug

When on Home page of a website Name of site is wrong , it is low severity bug as it is not going to affect the major functionality but since its the home page of the website it may create bad impression on customers.
Here it should be High Priority.

High Priority & Low Severity

If we want to take a printout of a page or any document then if Printer doesn’t allow us take prinout , it is a High Priority Bug as it is related to Functionality but since we can take the prinout from another Printer or we if can change the configuration then it is Low Severity Bug as we are getting our work done anyways without letting it affected by malfunctioning of Printer.

#27 sagar on 05.18.08 at 2:29 pm

it is really useful and interesting

#28 Boobalan on 05.19.08 at 5:15 am

Hi, i read your bug reporting, i can easily understand,
How i can write bug reporting.

And i can easily understand of the severity and priority.

I want to more examples for Severity and priority.

Can you please send my email .

#29 satyavir on 05.19.08 at 8:37 am

really it is elegant and intuitive report. thanks!

#30 vikas on 05.22.08 at 8:12 am

this very useful site..it can be very easily understandable …
thanks..

#31 Ramesh on 05.26.08 at 11:20 am

Hi could you pls any one share your experience in testing of Antivirus Testing scenarious ? that would be greatly appriciated

Regards,
Ramesh

#32 Rashmi on 05.28.08 at 7:12 am

Hi ,
This post is really helpful to imporve the way of reporting bug. Can you also explain a Bug Life cycle ?

#33 Rashmi on 05.28.08 at 7:12 am

Hi ,
This post is really helpful to imporve the way of reporting bug. Can you also explain a Bug Life cycle ?
Rashmi

#34 nisha arun on 05.31.08 at 9:20 am

hi, good articles. how many bugs (average) a tester can find in a day. i am getting an average of 10 to 11 bugs a day.

#35 Vijay on 05.31.08 at 3:36 pm

Hi Nisha,
You can’t estimate the number of bugs a tester can find in a day. There are so many factors on which the bug count is dependent such as: The complexity of AUT, Type of testing if it is functional, regression, load or UI testing.
How developer understood the requirements, developers coding ability, testers skill, level of application testing i.e if the application is being tested for first time or later versions. and so on..
So don’t judge your daily work on number of bugs unless you are getting paid on bug count ;-)

#36 Suresh Balakrishnan on 06.02.08 at 7:41 am

Hi Reema Karande,
This is suresh Working as a Test Engineer i have mentioned severity and Priority as below:

Defect severity determines the defect criticality whereas defect priority determines the defect immediacy or urgency of repair
 1. High Severity & Low Priority: Suppose there is an application which generates some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. In this application, there is a fault while calculating yearly report. This is a high severity fault but low priority because this fault can be fixed in the next release as a change request.
 2. Low Severity & High Priority: Suppose there is a spelling mistake or content issue on the homepage of BT.com website which has daily laks of hits all over UK. In this case, though this fault is not affecting the website or other functionalities but considering the status and popularity of the website in the competitive market it is a high priority fault.
 3. High Severity & High Priority: Suppose there is an application which gives some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. In this application, there is a fault while calculating weekly report. This is a high severity and high priority fault because this fault will hamper the functionality of the application immediately within a week. It should be fixed urgently.
 4. Low Severity & Low Priority: Suppose there is a spelling mistake on the pages which has very less hits throughout the month on any website. This fault can be considered as low severity and low priority.

Thanks,
Suresh Balakrishnan.
bsuresh7282@gmail.com

#37 Suresh Balakrishnan on 06.02.08 at 7:54 am

Hi Rashmi,
This is suresh Working as a Test Engineer i have mentioned Bug life cycle as below:

The different states of a bug can be summarized as follows:

1. New
2. Open
3. Assign
4. Test
5. Verified
6. Deferred
7. Reopened
8. Duplicate
9. Rejected and
10. Closed

Description of Various Stages:
1. New: When the bug is posted for the first time, its state will be “NEW”. This means that the bug is not yet approved.

2. Open: After a tester has posted a bug, the lead of the tester approves that the bug is genuine and he changes the state as “OPEN”.

3. Assign: Once the lead changes the state as “OPEN”, he assigns the bug to corresponding developer or developer team. The state of the bug now is changed to “ASSIGN”.

4. Test: Once the developer fixes the bug, he has to assign the bug to the testing team for next round of testing. Before he releases the software with bug fixed, he changes the state of bug to “TEST”. It specifies that the bug has been fixed and is released to testing team.

5. Deferred: The bug, changed to deferred state means the bug is expected to be fixed in next releases. The reasons for changing the bug to this state have many factors. Some of them are priority of the bug may be low, lack of time for the release or the bug may not have major effect on the software.

6. Rejected: If the developer feels that the bug is not genuine, he rejects the bug. Then the state of the bug is changed to “REJECTED”.

7. Duplicate: If the bug is repeated twice or the two bugs mention the same concept of the bug, then one bug status is changed to “DUPLICATE”.

8. Verified: Once the bug is fixed and the status is changed to “TEST”, the tester tests the bug. If the bug is not present in the software, he approves that the bug is fixed and changes the status to “VERIFIED”.

9. Reopened: If the bug still exists even after the bug is fixed by the developer, the tester changes the status to “REOPENED”. The bug traverses the life cycle once again.

10. Closed: Once the bug is fixed, it is tested by the tester. If the tester feels that the bug no longer exists in the software, he changes the status of the bug to “CLOSED”. This state means that the bug is fixed, tested and approved.

Thanks,
Suresh Balakrishnan.
bsuresh7282@gmail.com

#38 Anuradha on 06.02.08 at 10:04 am

Hi Friends ,

can anyone tell me process of testing procedure with example from starting the process till bug reporting.?

#39 Suresh Balakrishnan on 06.02.08 at 10:14 am

Hi Anuradha,

This is suresh working as a Test Engineer i have mentioned Testing Process as below:

1.Test Requirements:
• Requirement Specification documents
• Functional Specification documents
• Design Specification documents (use cases, etc)
• Use case Documents
• Test Trace-ability Matrix for identifying Test Coverage

2.Test Planning:
• Test Scope, Test Environment
• Different Test phase and Test Methodologies
• Manual and Automation Testing
• Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc
• Evaluation & identification – Test, Defect tracking tools

3.Test Environment Setup:
• Test Bed installation and configuration
• Network connectivity’s
• All the Software/ tools Installation and configuration
• Coordination with Vendors and others

4.Test Case Design:
• Test Traceability Matrix and Test coverage
• Test Scenarios Identification & Test Case preparation
• Test data and Test scripts preparation
• Test case reviews and Approval
• Base lining under Configuration Management

5.Test Case Execution and Defect tracking:
• Executing Test cases
• Testing Test Scripts
• Capture, review and analyze Test Results
• Raised the defects and tracking for its closure

6.Test Report and Acceptance:
• Test summary reports
• Test Metrics and process Improvements made
• Build release
• Receiving acceptance

Thanks,
Suresh Balakrishnan.
bsuresh7282@gmail.com

#40 Ramesh on 06.02.08 at 3:20 pm

1. Basically if build given by development team
2. Testing team will start the test
3. either start with installation test or general smoke test is done , to make sure that major functionality works fine as per the requirement & Regression testing is done I’ll continue in tomorrow

bye

#41 pravin mhatre on 06.03.08 at 9:03 am

Hi vijay Thyanks for giving me this valuable information.
Its very simple to understand will u give details of DOT NET TESTING.

#42 Anuradha on 06.03.08 at 9:04 am

Hi suresh ,

Thanks a lot for ur information.

Bye,

#43 Anuradha on 06.03.08 at 9:08 am

Hi Ramesh,

Thank u for ur information.

Bye,

#44 pravin mhatre on 06.03.08 at 9:08 am

Hi vijay Thanks for giving me this valuable information.
Its very simple to understand will u give me details of DOT NET TESTING.

#45 vinoth on 06.03.08 at 11:42 am

Hi Vijay ,

Give breif about “How to test in DOTNET TESTING”

#46 vinoth on 06.03.08 at 11:47 am

Can U Give breif about “How to test in DOTNET TESTING”

#47 vinoth on 06.03.08 at 11:50 am

Hi Vijay,

Can u give idea how to do “WHITEBOX TESTING” without knowing program.

#48 vinoth on 06.03.08 at 11:51 am

Hi Vijay,

Can u give idea how to do “WHITEBOX TESTING” without knowing program. Kindly reply me.

#49 Suresh Balakrishnan on 06.05.08 at 11:50 am

Hi Vinoth

I have mentioned Whitebox Testing and its types as given below:

White box testing strategy deals with the internal logic and structure of the code. White box testing is also called as glass, structural, open box or clear box testing. The tests written based on the white box testing strategy incorporate coverage of the code written, branches, paths, statements and internal logic of the code etc.

In order to implement white box testing, the tester has to deal with the code and hence is needed to possess knowledge of coding and logic i.e. internal working of the code. White box test also needs the tester to look into the code and find out which unit/statement/chunk of the code is malfunctioning.

Advantages of White box testing are:
i) As the knowledge of internal coding structure is prerequisite, it becomes very easy to find out which type of input/data can help in testing the application effectively.
ii) The other advantage of white box testing is that it helps in optimizing the code
iii) It helps in removing the extra lines of code, which can bring in hidden defects.

Disadvantages of white box testing are:
i) As knowledge of code and internal structure is a prerequisite, a skilled tester is needed to carry out this type of testing, which increases the cost.
ii) And it is nearly impossible to look into every bit of code to find out hidden errors, which may create problems, resulting in failure of the application.

Types of testing under White/Glass Box Testing Strategy:

Unit Testing:
The developer carries out unit testing in order to check if the particular module or unit of code is working fine. The Unit Testing comes at the very basic level as it is carried out as and when the unit of the code is developed or a particular functionality is built.

Static and dynamic Analysis:
Static analysis involves going through the code in order to find out any possible defect in the code. Dynamic analysis involves executing the code and analyzing the output.

Statement Coverage:
In this type of testing the code is executed in such a manner that every statement of the application is executed at least once. It helps in assuring that all the statements execute without any side effect.

Branch Coverage:
No software application can be written in a continuous mode of coding, at some point we need to branch out the code in order to perform a particular functionality. Branch coverage testing helps in validating of all the branches in the code and making sure that no branching leads to abnormal behavior of the application.

Security Testing:
Security Testing is carried out in order to find out how well the system can protect itself from unauthorized access, hacking – cracking, any code damage etc. which deals with the code of application. This type of testing needs sophisticated testing techniques.

Mutation Testing:
A kind of testing in which, the application is tested for the code that was modified after fixing a particular bug/defect. It also helps in finding out which code and which strategy of coding can help in developing the functionality effectively.

Besides all the testing types given above, there are some more types which fall under both Black box and White box testing strategies such as: Functional testing (which deals with the code in order to check its functional performance), Incremental integration testing (which deals with the testing of newly added code in the application), Performance and Load testing (which helps in finding out how the particular code manages resources and give performance etc.) etc.

Thanks,
Suresh
bsuresh7282@gmail.com

#50 munna on 06.08.08 at 12:04 pm

The information given about bug report is very useful to every tester .I want to know about the other bug tracking tool like Bugzilla.I want to know about the features of Bugzilla and what are the differences between Quality Center and Bugzilla.Cant we use Quality centre as a bug tracking toll
bye

#51 Vijaya Kawadkar on 06.08.08 at 4:37 pm

Quality Center is also a management and defect tracking tool like Test Director. There is one Tab called Defect Tab in it Which is used for Defect Trcking and Defect Reporting. It has Four tabs – Requirement, Test Plan, Test Lab and Defect which are similar to Four tabs of Test Director.

#52 iliyas on 06.11.08 at 7:26 am

Hi Vijay….!

Nice to ur see artical, its Very easy to understant for bignners …. can any body explain me about Test Acceptance Plan…..

Thanks
With Rgards….!

ILIYAS

S/W Test Engineer

iliyas@writesoon.com

#53 selvam on 06.11.08 at 2:01 pm

Hi Friends,

Currently i am working in Non-IT field and planned to switch my career to testing.I had learned the basics of testing,and now i am very eager to learn testing practically with real time projects.
If any one interested to teach testing personally with real time projects , i will be more grateful, or else show me the right place in chennai.
Thanks & regards
selvam.ba@rediffmail.com

#54 Satish on 06.17.08 at 6:28 am

Hi..Everybody..!

I am Satish working on Manual testing. I want to help the freshers and new testers by explaining the real time concepts of testing.

Add me to your messengers:satish_157@yahoo.com
157.satish@gmail.com

Regards,
Satish

#55 vishali on 06.17.08 at 2:09 pm

Hi
What type of testings we can automate

#56 vishali on 06.17.08 at 2:10 pm

When actually automation comes in to testing process

#57 Kavita on 06.18.08 at 12:03 pm

Vishali,

We can automate the functional testing, regression testing and performance testing.

Regards,

Kavita

#58 shyam on 06.25.08 at 7:31 am

Hi Everyone, can u helpme out in getting any free trail version of bug reporting tool, i try’d a lot but i didnot get anything, its better if u send a browser link

#59 Muthuraj on 07.13.08 at 5:54 pm

it is very easy to understand,thank you very much

#60 Abhishek Kumar on 07.20.08 at 8:42 am

What is the difference between Test Cases, Test Scenario, Test Script, Test Strategy & Test Plan.

#61 murali on 07.25.08 at 9:53 am

hai this is murali,

is manual testing of a application covers all the errors(100%) ?

#62 murali on 07.25.08 at 9:56 am

is automation tools are compulsary for testing?

#63 viji on 07.25.08 at 10:34 am

what is an expansion of QTP in testing tool.when we need for QTP test?

#64 Developers are not good testers. What you say? on 08.07.08 at 2:02 pm

[...] Optimistic developers – Yes, I wrote the code and I am confident it’s working properly. No need to test this path, no need to test that path, as I know it’s working properly. And right here developers skip the bugs. [...]

#65 Ramu Alladi on 08.12.08 at 1:00 pm

Good example.

#66 svarram on 08.25.08 at 2:11 am

Is there any certification I can take on Software Testing? Give me the details of the certifications and any relevant materials to read?

#67 srikanth jaligama on 09.10.08 at 12:56 pm

hi all,
this is srikanth jaligama working as software testengineer in hyd,
If all of u have any realtime queries, let us share knowledge, thanking u

#68 aatish on 09.30.08 at 9:43 am

The bug report is very easy to under stand and it is very useful.

#69 Murphy on 10.08.08 at 8:40 am

Nice write up all you guys!!

#70 Yolisa Ramokolo on 10.15.08 at 9:44 am

Thanks for the good job WELL DONE :-)

I have kept and wrote some notes of writting a professinal bug report.Before i used to use only an excel sheet with a few columns, but thanks to you today i can write a professional Bug Report.

Thank you once again.

#71 Sudhakaran on 11.19.08 at 6:39 am

Hi…
Its really easy to understand..thanks

#72 Anoo raadha on 11.20.08 at 8:44 am

Hi friends can anyone give me some sample testcases for Calendar(For example Google calendar).

#73 TEster on 11.25.08 at 12:19 pm

Hello anoo raadha..
first go infront of the calendar..and put ur hands in calendar leaves and then remove one by one.

#74 Anoo raadha on 11.25.08 at 3:10 pm

Thank you for your information TEster.
I had done it already.
I was asking about Google calendar or Microsoft outlook calendar.Not the Daily calendar.
My application is very related to Google calendar.I need some good test cases on that.If you can help please that I can apply those testcases to my application.

#75 Sanjana on 12.09.08 at 3:55 pm

Please help me to write the test startegy for the Enterprise Architecture system

#76 Sarang on 12.16.08 at 11:27 am

what is difference between system integration testing and system testing? ….plz anyone gives the exact answers

#77 VIKAS on 12.21.08 at 10:04 am

Hi Friends

All the information’s are useful specially Bug Report

Regrads,
Vikas

#78 Hina on 01.12.09 at 11:08 am

Hello Vijay,
Your post really simple and understandable…

#79 Seryein on 01.16.09 at 9:52 pm

I know this is an example, but i can not avoid make you an observation about your report that always has been a problem for us, is the fact that in the bug report is not included the data used for the test, in several ocasions some bugs cannot be reproduced by the developers because it occurrs with data with specific characteristics, then the developer try to reproduce the bug with any data and maybe he will not able to reproduce it, and will mark the bug as not reproduced or something else, wasting time in the process until the bug is reproduced, and finally fixed. The recomendation here, is always that it be possible, include in the bug report the basic data used for the test.

#80 sundar on 01.20.09 at 6:06 am

Hi Friends,
I have prepared one testing report. it covers bug tracking report and summary matrix, test case report. hereafter any other reports will need for manual testing?

#81 Anil on 03.10.09 at 9:35 am

Hi Vijay,
Very useful artical. I have learned all these things from my friend, if I read this artical earlier then there was no need to ask to friends. Anyway thanks a lot!!

#82 Soniya on 03.12.09 at 4:54 pm

Hi,
Thanks all for giving useful informations. I need to know how to create a bug report if the same bug occur again?
Ex: A while testing an application X, and report a bug about it in the A section (or category) of bug reports. Now I am testing application Y and get the same error .

#83 lucky on 03.13.09 at 5:13 am

@sonia

in this case you report the same bug in application Y
giving a reference to previous bug which was observed in application X.

if both applications belong same master application then you are suppose to give reference, other wise you need report the same bug in details with respect to application y as it is a different application than applicaton X.
hope you got it
still need clarification mail me at boldrps1479@gmail.com
we can discuss online

#84 Soniya on 03.13.09 at 6:11 pm

Thank you so much lucky, I got it.

#85 shivanand on 03.18.09 at 9:32 am

12 Given the following code, which is true about the minimum number of test cases required for full statement and branch coverage: Read P Read Q IF P+Q > 100 THEN Print “Large” ENDIF If P > 50 THEN Print “P Large” ENDIF
a) 1 test for statement coverage, 3 for branch coverage b) 1 test for statement coverage, 2 for branch coverage c) 1 test for statement coverage, 1 for branch coverage d) 2 tests for statement coverage, 3 for branch coverage e) 2 tests for statement coverage, 2 for branch coverage

please explain

#86 Shashi on 03.19.09 at 1:01 pm

Hi everyone,

Can you please tell me the difference between a bug report and a test cases report

Thanks in advance

#87 Reshma on 04.08.09 at 5:07 am

Hi Vijay,

You are really putting lots of efforts in providing these sort of help in Software Testing to all. Keep it up.
Can i get your email id, so that whatever question and quesries i have, i can mail you. if possible Revert pls…

#88 lucky on 04.08.09 at 8:40 am

hai sonia,

still if you have doubts on testing mail me at
below id okay.

lukcy

boldrps1479@gmail.com

#89 Neha Dudeja on 04.13.09 at 2:03 pm

Hi Vijay,

This was a very helpful sample for bug reporting.

Thanks,
Neha

#90 Neha Dudeja on 04.13.09 at 2:07 pm

Hi Vijay,

Could you please explain the difference between Severity and Priority. These two terms seem very confusing to me while reporting the bug?

Thanks,
Neha

#91 Vishal Garg on 07.02.09 at 10:57 am

Neha,

following is the difference between Severity & Priority:

Severity :
it shows the impact of a bug on the application. If any bug is there which is crashing the application then its a HIGH severity bug. If the bug is just a cosmic bug like spelling mistake or font size, color issue, then its a low severity bug.

Priority:
Priortity is time given to dev team to fix the bug. “HIGH” Priority means “bug to be fixed at the earliest”

Hope this’ll help u.

#92 VijayD on 07.02.09 at 9:13 pm

Hey Guys,

I’m back again, its been quite long time posting articles here. I am glad if I can help you guys.

#93 Subrahmanya Nayak on 08.07.09 at 6:03 am

Hi All,

Please answer me for the following question
1. In bangalore where i can get the training on Banking Domain?
2. Which Automation tool used to Testing Banking domain application?

Thanks & Regards
Subrahmanya Nayak
9886877192
subrahmanyadnayak@gmail.com

#94 muthu on 09.15.09 at 7:11 am

hello
Am a test engg fresher.
want to know more about quality control and scope it has?
what all certification should i do to get quality control job.

#95 priya on 10.13.09 at 6:03 pm

Hi,
Thanks for your posting. I am learning QA testing. I want to know how to report bug from a website?

#96 Vishal Garg on 10.14.09 at 4:38 am

Hi freinds,

Muthu,
QC has very vast scope..you can work as a manual test engineer (black box = testing without checking code), Manual test engr. (white box= testing checking code), Automation test engineer by automating the scripts & performance test engineer using performance testing tools.
There are a no. of certifications which you can go for e.g. CSTE, CSQA etc…

Priya
I have a lil doubt on ur question…do u mean reporting bug for a website??

#97 Dilip kumar on 10.21.09 at 6:38 am

Hi vijay,
It’s very nice. I hope everyone will get a standard bug report. thanks for your work

thanks,
Dilip.M

#98 Gabriel on 10.26.09 at 3:43 pm

Hi vijay,
Thanks for your work. This was a very helpful sample for bug reporting.

#99 sainaresh on 11.26.09 at 2:19 pm

Useful Information for Test Enggs

#100 sai on 01.07.10 at 11:07 am

can any one explain about priority and severity ?

#101 vidya on 01.12.10 at 12:51 pm

In simple terms, Severity is business (how severe is the damage to the company) and priority is technical.

#102 venkat on 01.28.10 at 9:20 am

hi Sai/ Vidya,

please check my comment also.

severity : how sever the bug affected the software system.(Testing Team)

1-Showstopper System severely impacted/not available – no workaround
2-Critical System available but certain function fails
3-Major Certain function fails with low impact, workaround available
4-Minor Minimal impact on system function, or cosmetic error

priority : Giving preference to severity .. say SEV1 should be done first, SEV2 should be done 2nd etc. (Developer Team)

thanks
venkat
eesan652@hotmail.com

#103 priyanka on 03.10.10 at 2:57 pm

hi vijayd
m going to upload my CV.m frresher so how much chances for getting me job.please help me…

#104 vikram on 04.02.10 at 5:40 am

Severity is the impact of the bug on the application

priority is to say how important the bug is to fix.

#105 Smitha on 04.21.10 at 9:52 am

Suresh,

The answers that you have given were easily understandable and remembrable….

Thanks!
Regards,
Smitha

#106 Roshin on 04.23.10 at 9:32 am

very Nice..Article!!!!!

#107 Rajesh on 05.01.10 at 11:57 am

Very fruitful for us

#108 irfan on 05.02.10 at 1:58 pm

hi,

this is irfan… i am very happy because you people providing or helping in our field with the good material whatever we need…

thank you.

#109 Deepthy Jijin on 05.18.10 at 11:18 am

Hi
A document in easy language.
Easy to understand and solve queries.
Thanks a lot for this.

May God Bless U

#110 Gowtha on 05.22.10 at 4:49 pm

Hi,
Thanks for all

#111 prasad on 05.26.10 at 1:21 pm

hi,
if any one can send me the BUG REPORTING template for any application.
means, the structure of the bug reporting template

#112 Mayasen on 06.04.10 at 4:48 am

Hi Prasad, #111

If you are looking for bug tracking tool, then you can go for some open-source tools like Mantis or Bugzilla. They are very easy to understand and use.

Otherwise you can create your own kind of tracking sheet using MS-excel.

Major elements which should present in your tracker are,

Bug ID, Test Case ID, Date of Reporting, Date of Resolved, Summary, Description, Steps-to-reproduce, Assigned to, Status, Severity, Priority and comments.

#113 Mayasen on 06.04.10 at 4:52 am

Hi Prasad, #111

You can also check,

http://www.softwaretestinghelp.com/sample-bug-reports-for-web-and-product-applications/

#114 Gayatri on 07.05.10 at 5:35 am

Very use full information .Thnaks.

#115 pratibha patil on 09.22.10 at 12:45 pm

if i found bug & reported to developer then he assign to me i did regression testing , after that for release 1 it has no bug but in second release there is bug then what should i do …? is regression or retesting?
plz explain me
my id is pratibha.patil30@gmail.com

#116 praveen kumar on 10.14.10 at 5:49 am

Hi

This example is very easy to understand and I understand it very clearly.
Thanks a lot for this.

Thanking U

#117 shankar on 11.15.10 at 10:51 am

It was very useful friend.Thank u so much to all…………..

#118 Web Testing: Complete guide on testing web applications « qa on 02.08.11 at 8:45 am

[...] ? Sample bug report [...]

#119 venkadesan on 03.01.11 at 6:50 am

hi

#120 satish on 03.08.11 at 5:54 pm

thank u

#121 sagar on 03.09.11 at 5:02 am

Hie……..
thanks for giving this information ,it is very usefull and easy to understand

#122 Shweta on 03.23.11 at 10:15 am

Hi, myself Shweta, I completed BscIT and passout in 2008. Currently working as a Software Tester and having nearby 7 months experience.

I like your all the articles.

Will u please suggest me any career opportunities in Software Testing. In Testing, I want to become on a top list but I don’t have way to reach their.

So, waiting for your reply.

Thanks,
Shweta

#123 Deepika on 06.21.11 at 3:06 pm

Hi
It is really very useful and easy to understand
thanks for giving this information and i expect that u will continue to sharing your knowledge and experience with us.
thanks :)

#124 sathish kumar on 07.29.11 at 5:51 pm

hi..
thankQ for ur bug reporting its very useful for me.

#125 kanth on 08.16.11 at 5:20 am

Very Useful Report Thank u

#126 saiprasad on 09.12.11 at 5:22 pm

This info is very useful ..thanks for the info mate ….

#127 srinivasan on 09.21.11 at 9:25 am

hi all, i got a wonderful info from u, & i want to know about Test bed, kindly help us

#128 roopa on 09.26.11 at 7:20 pm

hi vijay u r bug report post is easily understandable and helpful thanks

#129 Developers are not Good Testers.why? « sureshistqb on 09.28.11 at 10:48 am

[...] no need to test that path, as they know it’s working properly. And right here developers skip the bugs. Developer vs Tester: Developer always wants to see their code working properly. So they will test [...]

#130 subha on 10.16.11 at 2:52 am

Hi,
Vijay,

The bug Cycle Report was very simple and easy to understand.
thanks for posting/

#131 arun on 03.23.12 at 7:33 am

can anyone tell me about scope of web testing?

#132 Ajai prakash on 03.28.12 at 7:14 am

hii friends,
when i’m testing some websites i found some bugs but i don’t know whether it is a proper bug or not please conform it the bug is
when i restore down the browser i did’t get after screen fit tabs and images showing blank in some area whether it is a bug or not please clarify me

#133 Ricci on 04.10.12 at 8:16 am

this really helps! although, it is in the same manner of how we log our defects but your explanation teaches me how to be a better defect – logger:)

#134 sirisha on 05.18.12 at 9:25 am

very nice and Essayly Understanding The Report….Thank U Vijay.

#135 Suresh Sanga on 07.10.12 at 12:41 pm

Thanks Vijay….

U have provided such a good article for reporting a bug…..

If u have a time, u can also provide that how many ways do we have to find the bug in Web Application.

Thanks & Regards,
Suresh Sanga

#136 Yolisa Ramokolo on 10.02.12 at 2:05 pm

Hi Reema Karande,
This is Yolisa Ramokolo working as a Test Engineer at National Treasury. I have mentioned severity and Priority as below:

Defect severity determines the defect criticality whereas defect priority determines the defect immediacy or urgency of repair
1. High Severity & Low Priority: Suppose there is an application which generates some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. In this application, there is a fault while calculating yearly report. This is a high severity fault but low priority because this fault can be fixed in the next release as a change request.
2. Low Severity & High Priority: Suppose there is a spelling mistake or content issue on the homepage of BT.com website which has daily laks of hits all over SA. In this case, though this fault is not affecting the website or other functionalities but considering the status and popularity of the website in the competitive market it is a high priority fault.
3. High Severity & High Priority: Suppose there is an application which gives some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. In this application, there is a fault while calculating weekly report. This is a high severity and high priority fault because this fault will hamper the functionality of the application immediately within a week. It should be fixed urgently.
4. Low Severity & Low Priority: Suppose there is a spelling mistake on the pages which has very less hits throughout the month on any website. This fault can be considered as low severity and low priority.

Thank You,
Yolisa Ramokolo.

#137 Shankar Barnwal on 05.08.13 at 7:52 am

Can anyone tell me what is a test case, and send me some examples of Bug Reporting in manual testing.

#138 Mukesh on 05.13.13 at 12:37 pm

Can we report bug report without using any tracking tools?

tell me the clear answer with example?

#139 sandy on 05.28.13 at 7:37 pm

hi guys

Am Sandy here if anybody needs manual testing real time project for job reference, experience certificate in software testing with reliable background as well as other field also pl feel free to contact me

#140 dmr on 06.07.13 at 7:58 pm

hi sandy i want experience certificate in software testing.. plz contact me by mail. champdyuti@gmail.com

#141 Kev on 06.12.13 at 7:43 am

Hi guys
For the above Scenario, how to report a Bug in JIRA

#142 Aman on 07.18.13 at 5:05 am

Hi

Nice described the example the only thing that is missing is the Actual Result:

#143 Hussain Ashraf on 09.16.13 at 11:44 am

Hello Vijay,
Your post really simple and understandable.

Thanks…

#144 das on 09.19.13 at 10:05 pm

superb VIJAY KEEP IT UP

#145 amanda on 09.28.13 at 9:51 pm

its minecraft its not working

#146 vijay s on 02.07.14 at 5:46 am

Difference between mutation testing and regression testing????please help