1 / 12

INTRODUCTION

INTRODUCTION. QA Department business systems All the bug reports and all the bug tracking systems are very similar. BUG REPORTS. Why writing bug reports? Getting the bug fixed What makes a good bug report? How to reproduce the bug

deiter
Download Presentation

INTRODUCTION

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INTRODUCTION QA Department business systems All the bug reports and all the bug tracking systems are very similar

  2. BUG REPORTS Why writing bug reports? Getting the bug fixed What makes a good bug report? How to reproduce the bug Analyze the problem to minimize number of steps to reproduce it Complete, easy to understand, non-conflicting

  3. BUG REPORTS When should you write a bug report? Immediately upon identifying the bug Describe Content of the bug report? Short Description/Synopsis Steps to reproduce Severity Priority Status 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) Serious (workaround) Minor Suggestion/Enhancement

  5. BUG REPORTS Name 3 levels of priority? High Medium Low Who can assign/change severity or priority in a bug report? Tester assigns severity Development/Project Manager assigns Priority

  6. BUG REPORTS Why looking for most serious consequences of the bug? To assign higher severity (get higher priority) 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. The easier to understand – the better chances to have it fixed The faster the fix - the better the chance it will be done

  8. BUG REPORTS Things to remember: Look for configuration dependence Reproduce the bug before it is reported Is that first-time-only bug ?

  9. BUG TRACKING DATABASE Why do we need Bug Tracking Database? Accountability Communication tool Monitoring individual performance What is a prime objective of a Bug Tracking Database? To get the bugs fixed

  10. BUG TRACKING DATABASE Describe Bug's life cycle? Bug gets reported It goes to Development/Project Manager to get “Assigned To” and “Priority” Developer sees the report, fixes the bug, marks it as “Fixed” 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 a few other systems Compare the environments Reproduce on developer’s system Developer debugs on QA system

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

More Related