1. INTRODUCTION 1. 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 identifying the bug Immediately upon identifying the bug Describe Content of the bug report? Short Description/Synopsis Short Description/Synopsis Steps to reproduce Steps to reproduce Severity Severity Priority Priority Status Status Many more – see the bug reporting form Many more – see the bug reporting form

4. BUG REPORTS Name 4 levels of the seriousness of the problem (Severity)? Critical/Fatal (crash, data corruption, hang) Critical/Fatal (crash, data corruption, hang) Serious (workaround) Serious (workaround) Minor Minor Suggestion/Enhancement Suggestion/Enhancement

5. 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/Project Manager assigns Priority Development/Project Manager assigns Priority

6. 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? (discussion) What is reproducible bug? (discussion)

7. BUG REPORTS Why should tester look for simplest and most general conditions under which bug will be easily reproducible? Look for more than one path to a same problem. Look for more than one path to a 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

8. 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 ?

9. 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

10. BUG TRACKING DATABASE Describe Bug's life cycle? Bug gets reported Bug gets reported It goes to Development/Project Manager to get “Assigned To” and “Priority” It goes to Development/Project 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

11. BUG TRACKING DATABASE What happens if reported bug cannot be reproduced by a developer? Retest on your system Retest on your system Retest on a few other systems Retest on a few other systems Compare the environments Compare the environments Reproduce on developer’s system Reproduce on developer’s system Developer debugs on QA system Developer debugs on QA system

12. BUG TRACKING DATABASE What happens next after the bug is (allegedly) fixed? Validate the fix Validate the fix Do regression testing Do regression testing What does that mean Deferred Bug? Who can make a decision to defer a bug? Discussion Discussion