![A bug report requires clear instructions, so that others can consistently reproduce it. Many bugs require some
experimentation to find the exact steps that cause the problem you are trying to report. It is a good practice to
separate each problem separately instead of crumbling them altogether. It’s not recommended to use terms like “I
think” or “I believe”.
Title/Summary:
Title should be short, precise & simple. It should serve as a concise summary of what the bug is. Be specific while
writing the title. Specific Environment can be mentioned in brackets at the very beginning of the title.
Example:
Good: [IE] When the Device Boots into an Advanced Mode It Sends Notifications Twice.
Bad: System Crashes.
Priority:
Priority of a defect is related to how quickly a bug should be fixed. We can select the initial Priority but it will finally
be assessed by the development team. Example: Critical, Major, Moderate, Minor
Environment:
The details of Software/Firmware versions, Operation Systems, Browser Details and any other related to the test
environment must be mentioned. Following format can be used:
[Server]; [OS Version] [Software/Firmware Version]; [Carrier]; [Browser]; [Browser Version]
Example: Test Server (build=#1059); Win 7 Professional x64; Chrome V63/Firefox 16/ IE 11; Samsung S6 (Android 8.0 Oreo)
Affected Version/Fix Version/Sprint
Priority/SeverityEnvironment
Description
Steps to Reproduce
Expected Result
Actual Result
Attachments – Screenshot, Video, Configuration & Log file.](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Recommended
More Related Content
Similar to Bug Reporting Template
Similar to Bug Reporting Template (20)
Recently uploaded
Recently uploaded (20)
Bug Reporting Template
- 1. BUG REPORTING TEMPLATE SAZED MONSUR QA TEAM LEAD
- 2. A bug report requires clear instructions, so that others can consistently reproduce it. Many bugs require some experimentation to find the exact steps that cause the problem you are trying to report. It is a good practice to separate each problem separately instead of crumbling them altogether. It’s not recommended to use terms like “I think” or “I believe”. Title/Summary: Title should be short, precise & simple. It should serve as a concise summary of what the bug is. Be specific while writing the title. Specific Environment can be mentioned in brackets at the very beginning of the title. Example: Good: [IE] When the Device Boots into an Advanced Mode It Sends Notifications Twice. Bad: System Crashes. Priority: Priority of a defect is related to how quickly a bug should be fixed. We can select the initial Priority but it will finally be assessed by the development team. Example: Critical, Major, Moderate, Minor Environment: The details of Software/Firmware versions, Operation Systems, Browser Details and any other related to the test environment must be mentioned. Following format can be used: [Server]; [OS Version] [Software/Firmware Version]; [Carrier]; [Browser]; [Browser Version] Example: Test Server (build=#1059); Win 7 Professional x64; Chrome V63/Firefox 16/ IE 11; Samsung S6 (Android 8.0 Oreo) Affected Version/Fix Version/Sprint Priority/SeverityEnvironment Description Steps to Reproduce Expected Result Actual Result Attachments – Screenshot, Video, Configuration & Log file.
- 3. Description: A quick overview of what you were trying to do when the bug appeared. It’s not recommend to make the description too big. Example: Application crashes on clicking the delete button while creating a new asset, therefore unable to create a new asset in the application. Steps to Reproduce: A good bug report should clearly mention steps to reproduce. Example: 1. Launch the application 2. Go to the Shopping Cart 3. Click buy now Expected Results and Actual Result: It is necessary to outline what is the outcome of the test and what the use should expect. Example: Expected Results Clicking buy now should navigate the user to the payment page Actual Results Clicking buy now crashed the application. Attachments: Screenshot: A picture is worth a thousand words. Take a Screenshot at the instance of failure with proper captioning to highlight the defect. Highlight unexpected error messages with light red color. Video: Screen recording could be helpful. There are many tools available for screen recording like Camtasia studio, Snagit etc. Configuration/Logs: Relevant configuration and logs must be attached.