1. Bug Tracking

2. Definition
 Bug(software bug) - an
error, flaw, mistake, "undocumented
feature", failure, or fault in a computer
program that prevents it from behaving
as intended (e.g., producing an
incorrect result).
 Buggy - a program that contains a large
number of bugs, and/or bugs that
seriously interfere with its functionality.
 Bug tracking system (BTS)- a
software application that is designed to
help quality assurance and
programmers keep track of reported
software bugs in their work.

3. Definition
 Bug tracking - the process of reporting and
tracking the progress of bugs from discovery
through to resolution.
 Bug tracking workflow (lifecycle of a bug or
defect) – a diagram that describes the states of
the bug or defect from it is created to it is closed.
 Bug report – a report that details the bugs
found in a program.

4. Bug reporting advices
 Effective bug reporting is very important; a bug report that simply
says “it doesn't work” is not good enough. Accurate bug reports
are the most likely to be fixed.
 The main principles needed to be taken into account in order to
report a bug are:
 Be clear - explain it so others can reproduce the bug
 One bug per report
 No bug is too trivial to report - small bugs may hide big bugs
 Clearly separate fact from speculation

5. Bug reporting required information
 Summary:
Short description which describes defect in
general.
 Steps to reproduce the problem:
This should be a concise and minimal set of steps
which can be followed to reproduce the problem.
 Expected results:
This should describe the expected behavior or
expected results which will readily explain why
the problem is being reported when compared to
the actual results.
 Actual results:
This should describe what actually
happened, complete with any error
messages, stack traces, screen shots, log files
that show the outcome
 Environment:
The specifics of the environment in which the
problem occurred are needed to allow the
problem to be reproduced.

6. Bug reporting required information
 Priority
“how important the defect is from business
perspective” , determines the order in which
defects get fixed
 Severity
“how severe the defect is from software system’s
perspective”, reflects the actual or expected
impact on customer

7. Lifecycle of a bug
 Open - this issue is in the initial 'Open' state. In
Progress- this issue is being actively worked on at
the moment by the assignee.
 Resolved - a resolution has been taken, and it is
awaiting verification by reporter. From here issues
are either reopened and become reopened, are
marked verified, or are closed for good and marked
closed.
 Reopened - this issue was once resolved, but the
resolution was deemed incorrect. For example, a
Cannot Reproduce issue is reopened when more
information shows up and the issue is now
reproducible. From here issues are either marked In
Progress, Resolved or Closed.
 Closed - the issue is considered dead, the resolution
is correct. Any zombie issues who choose to walk
the earth again must do so by becoming reopened.

8. Popular Bug Tracking system
Seapine TestTrack Pro
Bugzilla
JIRA
Mantis
TrackStudio Enterprise
YouTrack

9. JIRA – bug tracking system
Proprietary issue tracking product, developed by Atlassian.
Used for bug tracking, issue tracking and project management.
The product name, JIRA, is not an acronym but rather a
truncation of "Gojira", the Japanese name for Godzilla. It has
been developed since 2002.

10. JIRA create new issue
On this screen we can create new issue (new bug)

11. JIRA view issue
On this screen we can view already created issue
and perform some actions by pressing appropriate buttons

12. JIRA issue navigator
On this screen we can view all issues
Issue filtered by settings and parameters in left sidebar

13. Thank You!