An effective bug report should contain the following: Title/Bug ID Environment Steps to Reproduce a Bug Expected Result Actual Result Visual Proof (screenshots, videos, text) of Bug Severity/Priority Title/Bug ID: The title should provide a quick description of the bug. For example, “ Distorted Text in FAQ section on <name> homepage ”. Assigning an ID to the bug also helps to make identification easier. Environment: Device Type : Hardware and specific device model. OS: OS name and version. Tester: Name of the tester who identified the bug. Software Version: The version of the software which is being tested, and in which the bug has appeared. Connection strength:If the bug is dependent on the internet connection (4G, 3G, WiFi, Ethernet) mention its strength at the time of testing. Rate of reproduction:The number of times the bug has been reproduced, with the exact steps involved in each reproduction. Steps to Reproduce a Bug: Number the steps clear...
Comments
Post a Comment