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“.
58 comments ↓
Hi Vijay,
This is reporing of very simple bug. But nice and easy to understand….
THANX……
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.
see there is always said for the making of the GUI.Could u please tell me briefly about it.
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.
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.
HI vijay
Nice effort by u.
Thanks
Simple and easily understand bug report and very useful
hi vijay.
The report is of great help for begginers like me. it’s easy to understand. Thanks. Keep providing such help.
Good explanation.Easy to understand.
Hiiiii
I’m Anil
Is available any tool for crash any web page?
And pls tell me about DB testing…..
Thanksss
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?
hello vijay..
very good we r pleasure to read.thanks
try to give a more complex scenario
Its very simple and easy to understand
Thanks
It’s very useful with me. Thanks Vijay
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……………
@Mahalakshmi,
Please provide the email ID.
Regards,
VijayD
This site is very usefull.Its very simple and easy to understand
Hi vijay
its very simple to understand will u give details of Bugzilla installation
very nice bug report
Very nice ! Thanks for the report !
Who sets the severity and priority for the bug?
Please anyone give idea , how can i get free demo version of QTP (or ) Winrunner.
hi
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
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.
it is really useful and interesting
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 .
really it is elegant and intuitive report. thanks!
this very useful site..it can be very easily understandable …
thanks..
Hi could you pls any one share your experience in testing of Antivirus Testing scenarious ? that would be greatly appriciated
Regards,
Ramesh
Hi ,
This post is really helpful to imporve the way of reporting bug. Can you also explain a Bug Life cycle ?
Hi ,
This post is really helpful to imporve the way of reporting bug. Can you also explain a Bug Life cycle ?
Rashmi
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.
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
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
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
Hi Friends ,
can anyone tell me process of testing procedure with example from starting the process till bug reporting.?
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
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
Hi vijay Thyanks for giving me this valuable information.
Its very simple to understand will u give details of DOT NET TESTING.
Hi suresh ,
Thanks a lot for ur information.
Bye,
Hi Ramesh,
Thank u for ur information.
Bye,
Hi vijay Thanks for giving me this valuable information.
Its very simple to understand will u give me details of DOT NET TESTING.
Hi Vijay ,
Give breif about “How to test in DOTNET TESTING”
Can U Give breif about “How to test in DOTNET TESTING”
Hi Vijay,
Can u give idea how to do “WHITEBOX TESTING” without knowing program.
Hi Vijay,
Can u give idea how to do “WHITEBOX TESTING” without knowing program. Kindly reply me.
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
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
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.
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
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
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
Hi
What type of testings we can automate
When actually automation comes in to testing process
Vishali,
We can automate the functional testing, regression testing and performance testing.
Regards,
Kavita
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
Leave a Comment