Bug tracking tool


Published on

Published in: Technology, News & Politics
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Bug tracking tool

  1. 1. Bug Tracking
  2. 2. Definition Bug(software bug) - anerror, flaw, mistake, "undocumentedfeature", failure, or fault in a computerprogram that prevents it from behavingas intended (e.g., producing anincorrect result). Buggy - a program that contains a largenumber of bugs, and/or bugs thatseriously interfere with its functionality. Bug tracking system (BTS)- asoftware application that is designed tohelp quality assurance andprogrammers keep track of reportedsoftware bugs in their work.
  3. 3. Definition Bug tracking - the process of reporting andtracking the progress of bugs from discoverythrough to resolution. Bug tracking workflow (lifecycle of a bug ordefect) – a diagram that describes the states ofthe bug or defect from it is created to it is closed. Bug report – a report that details the bugsfound in a program.
  4. 4. Bug reporting advices Effective bug reporting is very important; a bug report that simplysays “it doesnt work” is not good enough. Accurate bug reportsare the most likely to be fixed. The main principles needed to be taken into account in order toreport 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. 5. Bug reporting required information Summary:Short description which describes defect ingeneral. Steps to reproduce the problem:This should be a concise and minimal set of stepswhich can be followed to reproduce the problem. Expected results:This should describe the expected behavior orexpected results which will readily explain whythe problem is being reported when compared tothe actual results. Actual results:This should describe what actuallyhappened, complete with any errormessages, stack traces, screen shots, log filesthat show the outcome Environment:The specifics of the environment in which theproblem occurred are needed to allow theproblem to be reproduced.
  6. 6. Bug reporting required information Priority“how important the defect is from businessperspective” , determines the order in whichdefects get fixed Severity“how severe the defect is from software system’sperspective”, reflects the actual or expectedimpact on customer
  7. 7. Lifecycle of a bug Open - this issue is in the initial Open state. InProgress- this issue is being actively worked on atthe moment by the assignee. Resolved - a resolution has been taken, and it isawaiting verification by reporter. From here issuesare either reopened and become reopened, aremarked verified, or are closed for good and markedclosed. Reopened - this issue was once resolved, but theresolution was deemed incorrect. For example, aCannot Reproduce issue is reopened when moreinformation shows up and the issue is nowreproducible. From here issues are either marked InProgress, Resolved or Closed. Closed - the issue is considered dead, the resolutionis correct. Any zombie issues who choose to walkthe earth again must do so by becoming reopened.
  8. 8. Popular Bug Tracking systemSeapine TestTrack ProBugzillaJIRAMantisTrackStudio EnterpriseYouTrack
  9. 9. JIRA – bug tracking systemProprietary 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 atruncation of "Gojira", the Japanese name for Godzilla. It hasbeen developed since 2002.
  10. 10. JIRA create new issueOn this screen we can create new issue (new bug)
  11. 11. JIRA view issueOn this screen we can view already created issueand perform some actions by pressing appropriate buttons
  12. 12. JIRA issue navigatorOn this screen we can view all issuesIssue filtered by settings and parameters in left sidebar
  13. 13. Thank You!