WHAT IS A BUG ?
If your bug report is effective, chances are higher or more higher that it will get fixed, So fixing a bug is depended on how effectively reporting it
Reporting a bug is a not a hobby or a skill ,It will tell you how to achieve our skill on finding bugs on web applications or websites.
THE POINT OF WRITING BUG REPORT IS TO GET BUGS FIXED
If tester is not reporting bug correctly programmer will most likely reject the bug as irreproducible,This can hurt testers ability and time also.
What are the qualities of a good or evil software bug report ?
Anyone can write a bug report even script kindle can also write a bug report,But not everyone can write a effective bug report,The average bug report and a good bug report
How to distinguish a bad or good bug report ?
It is simple ,apply techniques and characteristics to report a bug
How to Report a Bug To Companies?
Use Always Simple Bug report Template :
Well This is a simple bug report format, if you are writing bug report manually then some fields should need to specifically mention like bug number which should be assigned manually... For bug reporting use Bug report Tool.
Reporter : Your Name and mail address.
Ex : Madhan Raj M and M*****7@gmail.com
Product : In which product you found this bug
Ex : Facebook,Twitter,Google,etc...
Version : The product version if any
Component : These are the major sub modules of the product
Platform : Mention the hardware platform where you found this bugs.The Various platforms like Mac,HP,PC,Sun etc...
Operating System:
Mention all operating systems where you found the bug. operating systems like Linux,Unix,SunOs,Mac os,Windows.
Mention the different OS versions also if applicable like windows NT, Windows 2000, Windows XP etc..
Priority :
When bug should be fixed ? Priority is generally set from P1 to P5 as fix the bug with highest priority and P5 as Fix when time permits.
Severity : This describes the impact of the Bug
Types of Severity
When you are logging the bug in any bug tracking system then by default the bug status is new
Later on bug goes through various stages like FixedmReopen,Verified,Won't Fix etc..
Assign to:
If you know which developer is responisible for that particular module in which bug occured,else keep it blank this will assign bug to module owner or manager will assign bug to developer,possibly add the manager email address in cc list,then you can specify email address of that developer.
URL:
The page url on which bug occured
Summary:
A brief summary of the bug mostly in 80 or below words. Make sure your summary is reflecting what the problem is and where it is.
Description:
A detailed description of bug, Use following fields for description field:
Actual result : What is the actual result on running above steps
Expected result: How application should behave on above mentioned steps
Reproduce steps: Clearly mention the steps to reproduce the bug
These are the important steps in bug report, You can also add the report type as one more field which will describe the bug type.
The report Types are Typically
If your bug report is effective, chances are higher or more higher that it will get fixed, So fixing a bug is depended on how effectively reporting it
Reporting a bug is a not a hobby or a skill ,It will tell you how to achieve our skill on finding bugs on web applications or websites.
THE POINT OF WRITING BUG REPORT IS TO GET BUGS FIXED
If tester is not reporting bug correctly programmer will most likely reject the bug as irreproducible,This can hurt testers ability and time also.
What are the qualities of a good or evil software bug report ?
Anyone can write a bug report even script kindle can also write a bug report,But not everyone can write a effective bug report,The average bug report and a good bug report
How to distinguish a bad or good bug report ?
It is simple ,apply techniques and characteristics to report a bug
- Having clear and uniform specified bug
- Reproducible
- Be Specific
How to Report a Bug To Companies?
Use Always Simple Bug report Template :
Well This is a simple bug report format, if you are writing bug report manually then some fields should need to specifically mention like bug number which should be assigned manually... For bug reporting use Bug report Tool.
Reporter : Your Name and mail address.
Ex : Madhan Raj M and M*****7@gmail.com
Product : In which product you found this bug
Ex : Facebook,Twitter,Google,etc...
Version : The product version if any
Component : These are the major sub modules of the product
Platform : Mention the hardware platform where you found this bugs.The Various platforms like Mac,HP,PC,Sun etc...
Operating System:
Mention all operating systems where you found the bug. operating systems like Linux,Unix,SunOs,Mac os,Windows.
Mention the different OS versions also if applicable like windows NT, Windows 2000, Windows XP etc..
Priority :
When bug should be fixed ? Priority is generally set from P1 to P5 as fix the bug with highest priority and P5 as Fix when time permits.
Severity : This describes the impact of the Bug
Types of Severity
- Blocker : No further testing work can be done
- Critical : Application crash/Loss of data
- Minor : Minor loss of function
- Trivial : Some UI enhancements
- Major : Major loss of function
- Enhancement : Request for new feature or some enhancement in exisiting one
When you are logging the bug in any bug tracking system then by default the bug status is new
Later on bug goes through various stages like FixedmReopen,Verified,Won't Fix etc..
Assign to:
If you know which developer is responisible for that particular module in which bug occured,else keep it blank this will assign bug to module owner or manager will assign bug to developer,possibly add the manager email address in cc list,then you can specify email address of that developer.
URL:
The page url on which bug occured
Summary:
A brief summary of the bug mostly in 80 or below words. Make sure your summary is reflecting what the problem is and where it is.
Description:
A detailed description of bug, Use following fields for description field:
Actual result : What is the actual result on running above steps
Expected result: How application should behave on above mentioned steps
Reproduce steps: Clearly mention the steps to reproduce the bug
These are the important steps in bug report, You can also add the report type as one more field which will describe the bug type.
The report Types are Typically
- Coding error
- Design error
- Hardware problem
- Documentation issue
- New suggestion
Post a Comment
Thank you for visiting Afridi's Technoworld