Download presentation
Presentation is loading. Please wait.
Published byAmia Parsons Modified over 11 years ago
1
INTRODUCTION 1. Business systems and QA Department business systems 2. All the bug reports and all the bug tracking systems are very similar
2
BUG REPORTS Why writing bug reports? Getting the bug fixed Getting the bug fixed What makes a good bug report? How to reproduce the bug How to reproduce the bug Analyze the problem to minimize number of steps to reproduce it Analyze the problem to minimize number of steps to reproduce it Complete, easy to understand, non-conflicting Complete, easy to understand, non-conflicting
3
BUG REPORTS When should you write a bug report? Immediately upon finding the bug Immediately upon finding the bug Name 4 levels of (Severity)? Critical/Fatal (crash, data corruption, hang) Critical/Fatal (crash, data corruption, hang) Serious (workaround) Serious (workaround) Minor Minor Suggestion/Enhancement Suggestion/Enhancement
4
BUG REPORTS Name 3 levels of priority? High High Medium Medium Low Low Who can assign/change severity or priority in a bug report? Tester assigns Severity Tester assigns Severity Development Manager assigns Priority Development Manager assigns Priority
5
BUG REPORTS Why looking for most serious consequences of the bug?? To assign higher severity (get higher priority) To assign higher severity (get higher priority) What is reproducible bug?
6
BUG REPORTS Why should tester look for simplest and most general conditions under which bug will be easily reproducible? We have to look for more than just one path to the same problem. We have to look for more than just one path to the same problem. The easier to understand – the better chances to have it fixed The easier to understand – the better chances to have it fixed The faster the fix - the better the chance it will be done The faster the fix - the better the chance it will be done Management pays lots of attention to high visibility routine bugs Management pays lots of attention to high visibility routine bugs
7
BUG REPORTS Things to remember: Look for configuration dependence Look for configuration dependence Reproduce the bug before it is reported Reproduce the bug before it is reported Is that first-time-only bug ? Is that first-time-only bug ?
8
BUG TRACKING DATABASE Why do we need Bug Tracking Database? Accountability Accountability Communication tool Communication tool Monitoring individual performance Monitoring individual performance What is a prime objective of a Bug Tracking Database? To get the bugs fixed To get the bugs fixed
9
BUG TRACKING DATABASE Describe Bug's life cycle? Bug gets reported Bug gets reported It goes to Development Manager to get Assigned To and Priority It goes to Development Manager to get Assigned To and Priority Developer sees the report, fixes the bug, marks it as Fixed Developer sees the report, fixes the bug, marks it as Fixed It goes to Tester for verification of the fix It goes to Tester for verification of the fix What happens if reported bug cannot be reproduced by a developer?
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.