defect management

58
Defect Management by : Pankamol Srikaew 5410546181 Marisa Singwongwatana 5410546296 Chanon Khamronyutha 5410546041

Upload: pankamol-srikaew

Post on 09-Jan-2017

593 views

Category:

Software


0 download

TRANSCRIPT

Page 1: Defect management

Defect Management

by :Pankamol Srikaew 5410546181Marisa Singwongwatana 5410546296Chanon Khamronyutha 5410546041

Page 2: Defect management

What is DEFECT ?

Page 3: Defect management

“While testing when a tester executes the test cases he might observe that the actual test results do not match from the expected results. The variation in the expected and actual results is known as defects”

- softwaretestingmentor.com

Page 4: Defect management

“A software defect is a deficiency in a software product that causes it to perform unexpectedly. From a software user’s perspective, a defect is anything that causes the software not to meet their expectations”

- The Practical Guide to Defect Prevention, SafariBooksOnline.com

Page 5: Defect management

What is DEFECT?

Page 6: Defect management

What is DEFECT?

Page 7: Defect management

What is DEFECT?

Page 8: Defect management

What is DEFECT?

Page 9: Defect management

What is DEFECT?

Page 10: Defect management

What is DEFECT?

Page 11: Defect management

Bug or Defect ?

Page 12: Defect management

“A mistake in coding is called error, error found by tester is called defect,

defect accepted by development team then it is called bug,build does not meet the requirements then it Is failure.”

- tfortesting.wordpress.com

Page 13: Defect management

BugA fault in a program which causes the program to perform in an unintended or unanticipated manner.Bug is terminology of Tester.

DefectCommonly refers to several troubles with the software products, with its external behavior or with its internal features.

- tfortesting.wordpress.com

Page 14: Defect management

“A bug is the result of a coding error

A defect is a deviation from the requirements”

A defect does not necessarily mean there is a bug in the code

- Dan McGrath, stackexchange.com

Page 15: Defect management

“Not all software defects are caused by

coding errors”

- Software Testing, Wikipedia

Page 16: Defect management

Why there are defect in Software ?

Page 17: Defect management

“ Miscommunication of requirements introduces error in code “

“ Unrealistic time schedule for development “

Page 18: Defect management

“ Lack of designing experience “

“ Lack of coding practices experience “

Page 19: Defect management

“ Human factors introduces errors in code“

“ Lack of version control “

Page 20: Defect management

“ Buggy third-party tools “

“ Last minute changes in the requirement introduce error ”

Page 21: Defect management

“ Poor Software testing skill “

Page 22: Defect management
Page 23: Defect management

Defect Type

Page 24: Defect management

Defect Type

Requirement Coding

Graphic Design Tester

Data TestOther

Page 25: Defect management

Defect Type

Requirement

“defect from changing requirement without notify

other concerned team”

Page 26: Defect management

Defect Type

Coding

“defect that cause by developer team that didn’t

inspect the code ”

Page 27: Defect management

Defect Type

Graphic Design

“defect from unsuitable environment or after

composing the design with code the graphic perform

incorrectly ”

Page 28: Defect management

Defect Type

Tester

“defect from testers’ mistake or misunderstanding”

Page 29: Defect management

Defect Type

Data Test

“defect from test data which not cover that environment or the system is not support

that data”

Page 30: Defect management

Defect Type

Other

“system constraintenvironment constraint

etc.”

Page 31: Defect management

Defect Severity

Page 32: Defect management

Critical:

The defect affects critical functionality or critical data. It does not have a

workaround. Example: Unsuccessful installation, complete failure of a feature.

Defect Severity

Page 33: Defect management

Major:

The defect affects major functionality or major data. It has a workaround but is

not obvious and is difficult. Example: A feature is not functional from one module but

the task is doable if 10 complicated indirect steps are followed in another modules.

Defect Severity

Page 34: Defect management

Minor:

The defect affects minor functionality or non-critical data. It has an easy

workaround. Example: A minor feature that is not functional in one module but the

same task is easily doable from another module.

Defect Severity

Page 35: Defect management

Trivial:

The defect does not affect functionality or data. It does not even need a

workaround. It does not impact productivity or efficiency. It is merely an

inconvenience. Example: Petty layout discrepancies, spelling/grammatical errors.

Defect Severity

Page 36: Defect management

Defect Priority

Page 37: Defect management

UrgentHigh

MediumLow

Defect Priority

Page 38: Defect management

Business need for fixing the defect

Severity/Impact

Probability/Visibility

Available Resources

Available Time

Way to consider the defect priority

Page 39: Defect management

Defect Probability

Page 40: Defect management

● High

● Medium

● Low

Defect Probability

Page 41: Defect management

Defect Report

Page 42: Defect management
Page 43: Defect management

Good Defect Report

Be specificBe detailedBe objective

Reproduce the defectReview the report

Page 44: Defect management

Defect Life Cycle

Page 45: Defect management

New Tester finds a defect and posts it

AssignedDefect is assigned to the Development Team

DeferredDecided to be fixed in upcoming releases

Dropped Defect is found to be invalid

Defect Status

CompletedDefect is now fixed

ReassignedThe Fixed Defect is not fixed

ClosedDefect is indeed fixed

Page 46: Defect management

Defect Life Cycle

Page 47: Defect management

Defect tracking is process of tracking the logged defects in a

product from beginning to closure.

helps managing , evaluating and prioritizing defects when large number of defects is needed to be track over extended periods.

Defect Tracking

Page 48: Defect management

Defect Management Tools - Tools use in defect tracking system.

Core features :

● Provides a centralized repository for tracking defects across projects.

● Provides automated notifications of resource assignments.

● Ability to define defect resolution status in order to map back to your defect management process.

● Ability to provide management reporting, number of open defects grouped by various criteria.

Defect Management Tools

Page 49: Defect management

Github Issues Tracker

● https://www.youtube.com/watch?v=TJlYiMp8FuY

Defect Management Tools

Page 50: Defect management

HAPPYQUIZ

Page 51: Defect management

Where we can find the defects and Why?

Page 52: Defect management

WHY we have to prioritize defects?

HOW to prioritize them?

Page 53: Defect management

Why we have to make a defect report?How to write

a GOOD report?

Page 54: Defect management

Is it necessary that if there is the defect, it will only show up at the user

interface and Why?

Page 55: Defect management

What are the type of defect base on defect severity ?

Page 56: Defect management

What are the benefit of defect management ?

Page 57: Defect management

More resources...Defect Managementhttp://www.defectmanagement.com/defectmanagement/index.htm

Software bughttp://en.wikipedia.org/wiki/Software_bug

Defect by SoftwareTestingFundamentals.comhttp://softwaretestingfundamentals.com/defect/

Defect Life Cyclehttp://istqbexamcertification.com/what-is-a-defect-life-cycle/

And

Page 58: Defect management

HAVE FUN

WITH DEFECT

MANAGEMENT!!!!