introduction

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

Upload: baxter-kemp

Post on 31-Dec-2015

13 views

Category:

Documents


0 download

DESCRIPTION

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 - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: INTRODUCTION

INTRODUCTIONINTRODUCTION

1.1. QA Department business QA Department business systemssystems

2.2. All the bug reports and all the All the bug reports and all the bug tracking systems are very bug tracking systems are very similarsimilar

Page 2: INTRODUCTION

BUG REPORTSBUG REPORTSWhy writing bug reports?Why writing bug reports? Getting the bug fixedGetting the bug fixed

What makes a good bug What makes a good bug report?report?

How to reproduce the bugHow to reproduce the bug Analyze the problem to Analyze the problem to

minimize number of steps to minimize number of steps to reproduce itreproduce it

Complete, easy to understand, Complete, easy to understand, non-coflictingnon-coflicting

Page 3: INTRODUCTION

BUG REPORTSBUG REPORTSWhen should you write a bug When should you write a bug

report? report? Immediately upon identifying the Immediately upon identifying the

bugbug

Describe Content of the bug Describe Content of the bug report?report?

Short Description/SynopsisShort Description/Synopsis Steps to reproduceSteps to reproduce SeveritySeverity PriorityPriority StatusStatus Many more – see the bug reporting Many more – see the bug reporting

formform

Page 4: INTRODUCTION

BUG REPORTSBUG REPORTSName 4 levels of the Name 4 levels of the

seriousness of the problem seriousness of the problem (Severity)?(Severity)?

Critical/Fatal (crash, data Critical/Fatal (crash, data corruption, hang)corruption, hang)

Serious (workaround)Serious (workaround) MinorMinor Suggestion/EnhancementSuggestion/Enhancement

Page 5: INTRODUCTION

BUG REPORTSBUG REPORTSName 3 levels of priority?Name 3 levels of priority? HighHigh MediumMedium LowLow

Who can assign/change Who can assign/change severity or priority in a bug severity or priority in a bug report?report?

Tester assigns severityTester assigns severity Development/Project Manager Development/Project Manager

assigns Priorityassigns Priority

Page 6: INTRODUCTION

BUG REPORTSBUG REPORTSWhy looking for most serious Why looking for most serious

consequences of the bug? consequences of the bug? To assign higher severity (get To assign higher severity (get

higher priority)higher priority)

What is reproducible bug? What is reproducible bug? (discussion) (discussion)

Page 7: INTRODUCTION

BUG REPORTSBUG REPORTSWhy should tester look for Why should tester look for

simplest and most general simplest and most general conditions under which bug conditions under which bug will be easily reproducible? will be easily reproducible?

Look for more than one path to a same Look for more than one path to a same problem.problem.

The easier to understand – the better The easier to understand – the better chances to have it fixedchances to have it fixed

The faster the fix - the better the chance it The faster the fix - the better the chance it will be donewill be done

Page 8: INTRODUCTION

BUG REPORTSBUG REPORTSThings to remember:Things to remember: Look for configuration Look for configuration

dependencedependence Reproduce the bug before it is Reproduce the bug before it is

reportedreported Is that first-time-only bugIs that first-time-only bug ? ?

Page 9: INTRODUCTION

BUG TRACKING BUG TRACKING DATABASEDATABASE

Why do we need Bug Tracking Why do we need Bug Tracking Database?Database?

AccountabilityAccountability Communication toolCommunication tool Monitoring individual performanceMonitoring individual performance

What is a prime objective of a Bug What is a prime objective of a Bug Tracking Database?Tracking Database?

To get the bugs fixedTo get the bugs fixed

Page 10: INTRODUCTION

BUG TRACKING BUG TRACKING DATABASEDATABASE

Describe Bug's life cycle?Describe Bug's life cycle? Bug gets reportedBug gets reported It goes to Development/Project It goes to Development/Project

Manager to get “Assigned To” and Manager to get “Assigned To” and “Priority”“Priority”

Developer sees the report, fixes the Developer sees the report, fixes the bug, marks it as “Fixed”bug, marks it as “Fixed”

It goes to Tester for verification of the It goes to Tester for verification of the fixfix

Page 11: INTRODUCTION

BUG TRACKING BUG TRACKING DATABASEDATABASE

What happens if reported bug What happens if reported bug cannot be reproduced by a cannot be reproduced by a developer?developer?

Retest on your systemRetest on your system Retest on a few other systemsRetest on a few other systems Compare the environmentsCompare the environments Reproduce on developer’s Reproduce on developer’s

systemsystem Developer debugs on QA systemDeveloper debugs on QA system

Page 12: INTRODUCTION

BUG TRACKING BUG TRACKING DATABASEDATABASE

What happens next after the bug is What happens next after the bug is (allegedly) fixed?(allegedly) fixed?

Validate the fixValidate the fix Do regression testingDo regression testing

What does that mean Deferred Bug? What does that mean Deferred Bug? Who can make a decision to defer Who can make a decision to defer a bug?a bug?

DiscussionDiscussion