Defect tracking

Содержание

Слайд 2

Definitions Why do we need defect reports? Defect Life Cycle Defect

Definitions
Why do we need defect reports?
Defect Life Cycle

Defect Report
Defect Reporting Tips
Defect Tracking Tools. Jira

Agenda

Слайд 3

Definitions Mistake (Error) - human action that produces incorrect result Defect

Definitions

Mistake (Error) - human action that produces incorrect result

Defect (Bug, Fault)

- a flaw in a component or system that can cause the component or system to fail to perform its required function

Deviation from expected result

Incident - any event occurring that requires investigation

Слайд 4

Definitions Defect Report - a document reporting on any flaw in

Definitions

Defect Report - a document reporting on any flaw in a

component or system that can cause the component or system to fail to perform its required function.

Defect is considered as reported if:
it is entered into Defects Database
it contains enough information to reproduce and analyze it

Слайд 5

Why do we need Defect reports? To provide programmers, managers and

Why do we need Defect reports?

To provide programmers, managers and others

with detailed information about the behavior observed and the defect.
To support the analysis of trends in aggregate defect data, either for understanding more about a particular set of problems or tests or for understanding and reporting the overall level of system quality.
Give information that can lead to development and test process improvements
Слайд 6

Defect Life Cycle In Progress Detection Reporting Fixing Retesting Closure Assigning

Defect Life Cycle

In Progress

Detection

Reporting

Fixing

Retesting

Closure

Assigning

Failed Verification

Not An Issue

Won’t Fix

Not Reproducible

Reopening

Closed

Rejecting

Open

In

Progress

Reporting

Resolved

Слайд 7

Test Incident Report (Defect Report) According to IEEE 829 Test Incident

Test Incident Report (Defect Report)

According to IEEE 829 Test Incident Report

consists of:

Test Incident Report identifier
Summary
Incident Description
Inputs
Expected Results
Actual Results
Anomalies
Date and Time
Procedure Step
Attempts to Repeat
Testers
Observers
Impact
Severity
Priority

Слайд 8

Severity and Priority Severity – the degree of impact that a

Severity and Priority

Severity – the degree of impact that a defect

has on the development or operation of a component or system

Impact on functionality
How serious is the bug?

Scheduling
How soon to fix the bug?

Priority - the level of business importance assigned to an item, e.g. defect

Слайд 9

Try to reproduce symptoms when you see them Try to isolate

Try to reproduce symptoms when you see them
Try to isolate the

defect by making carefully chosen changes to the steps used to reproduce it
Ensure that this bug is not reported yet
Gather as many details as you can:
Put down Build# and Environment
Make a screenshot or even a video
Gather error logs if any
Be clear and unambiguous. Be neutral, fact-focused and impartial
Report all defect, you have observed

Defect Reporting Tips

Слайд 10

Defect Tracking Tool - a tool that facilitates the recording and

Defect Tracking Tool - a tool that facilitates the recording and

status tracking of defects and changes.
They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities.

Defect Tracking Tools

Defect tracking tools used at SoftServe projects:
Seapine TestTrack Pro
Bugzilla
FogBugz
JIRA
Mantis
Team Foundation Server (TFS)
and many others…

Слайд 11

Defect Tracking Tools Collect defect/request records Assign defect/request record to the

Defect Tracking Tools

Collect defect/request records
Assign defect/request record to the responsible

person
Collect defect/request history
Find defect/request by defined condition
Filter defect/request list by defined condition
Close defect/request record
Additionally, export defects
Слайд 12

Defect Tracking Tool Defect Reporting 1. Click Create Issue

Defect Tracking Tool

Defect Reporting
1. Click Create Issue


Слайд 13

Defect Tracking Tool 2. Select ‘Issue type’ = “Bug” 3. Set short and clear Summary

Defect Tracking Tool


2. Select ‘Issue type’ = “Bug”
3. Set short

and clear Summary
Слайд 14

Defect Tracking Tool 4. Select Priority* of the defect 5. Select

Defect Tracking Tool


4. Select Priority* of the defect
5. Select

component,
where you’ve found the defect,
and affected version
Originally, JIRA did have both
a Priority and a Severity field. 
The Severity field was removed
for a number of reasons […]
In order to re-implement Severity,
you can create a select-list custom field
Слайд 15

Defect Tracking Tool 6. Put down Description, Steps, Actual and Expected

Defect Tracking Tool


6. Put down Description, Steps,
Actual and Expected

results
into Description field
7. Set all other fields like
estimate or Documentation link
8. Attach screenshots, logs, etc.
9. Assign to appropriate person
10. Click ‘Save’ button
Слайд 16

Defect Tracking Tool Defect filtering Use configurable filter to find defect

Defect Tracking Tool


Defect filtering
Use configurable filter to find defect

by its parameter
Use quick search to open exact item if you know its number
Слайд 17

Defect Tracking Tool Other features Use link icon to get permanent

Defect Tracking Tool

Other features
Use link icon to get permanent link

of your unsaved filter
Use share button to share filter with other team members
Use bulk change if you need to make same change for numerous defects (i.e. change release or assignments)
Use views menu to set up defect list view


All these filtering abilities are very helpful for
defects analysis and statistic gathering