Bug Report White Paper

1828 Words4 Pages

White Paper White Paper on Art of Bug Reporting Nov’15 Table of Contents 1. Introduction 1 2. Content of BUG 1 3. Important aspect of each field with examples………………………………………………………………………………4 4. Efficient participation in Software Version Control Meetings 5 5. Impact of not making Bug properly 6 6. Conclusion 6 7. About the Author 7 1. Introduction Isn’t it obvious that any bug logged in a bug management system should be fixed by the developers? The answer is No. Factors like time to market the product, time to complete project on schedule and developers working in impractical tight schedules etc. force companies to release the product with few bugs which won’t affect the user largely. Who gives the confidence …show more content…

Look at the summary and discuss the impact of the bug on the user’s experience on using software product. 3. Based on the risk and impact assessment set the priority and assign the bug to appropriate developer for fixing the same. During step #2, it is imperative that every test engineer advocate the bug’s impact on the user experience if the bug doesn’t receive the priority it deserves. After all, it is we test engineers who consider the point of view of a user to write test cases and to test the product. Consider the example issue of not displaying the digits after decimal point in a banking domain. To a developer, it may seem like a less severe issue. He might argue that instead of declaring the variable as an integer, he’d declare that as a floating point to solve the issue and hence less severe. Tester role is explaining customer’s situation. Tester’s point should be how the user would complain in this scenario. The tester should say that, this will cause panic among the users as the customer loses his money in cents. 4. Impact of not marketing a bug properly If a bug is not marketed properly it will create issues like: 1. Incorrect defect priority 2. Delay in fixing the important …show more content…

It is more like developing a brand value for tester. In the initial phase of tester’s career, if tester can keep number of “Cannot Reproduce” or “Need more Info” or “Not a Valid Bug” or changes in severity as low as possible, at one stage bugs will not be scrutinized at all and they’d be directly assigned to the appropriate developer to be fixed. To develop such brand value and to win the confidence of tester team and the development and/or management teams, tester needs to develop technical skills in terms of testing knowledge, domain and communication skills. 5. Conclusion Any product or service, big or small, without proper advertising it is always bound to fail. Once a brand is established, any small product can be a super hit with the audience. Having said that, over-advertising a product can also cause damage to the reputation. So, a bug should always be written in a clear, concise and precise manner so that it gives an exact location of bug in the extensive/exhaustive software map. I reiterate that, this not only improves the quality of software but also reduces the cost of testing and developing the software to a great extent. Okay Now! Let’s go and get bugs fixed right

Open Document