Published on

Bugzilla is a defect tracking tool.

Published in: Technology
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Bugzilla Prepared By : Charul Bhan
  2. 2. Introduction <ul><li>Web-based general purpose bugtracker tool </li></ul><ul><li>Released as open source software by Netscape Communications in 1998 </li></ul><ul><li>Originally written in Tcl, later ported to Perl before its release as part of Netscape's early open source code </li></ul>Bugzilla Lifecycle
  3. 3. Main Page
  4. 4. Create user <ul><li>For creation of new account, first user has to submit his email address to administrator. </li></ul><ul><li>Administrator provides him the link to create a password with email address as a user name. </li></ul>
  5. 5. User Permissions
  6. 6. User Permissions Contd…
  7. 7. Add User <ul><li>From the main page, select the users link provided at the bottom of the page. </li></ul>
  8. 8. Add User Contd…
  9. 9. Add User Contd…
  10. 10. Email Preferences Prepared By : Charul Bhan
  11. 11. Email Preferences <ul><li>User can use email notification to keep himself informed about the various changes taking place in the bug. </li></ul><ul><li>These preferences are user configurable so that any user can customized it to his own needs. </li></ul>
  12. 12. Email Preferences Contd…
  13. 13. Email Preferences Contd…
  14. 14. Bugzilla Intricacies Prepared By : Charul Bhan
  15. 15. Definitions <ul><li>Product </li></ul><ul><li>A Product is a broad category of types of bugs, normally representing a single piece of software or entity. </li></ul><ul><li>They can be considered as the project under one domain. </li></ul><ul><li>Components </li></ul><ul><li>A Component is a subsection of a Product. It should be a narrow category, tailored to an organization. All Products must contain at least one Component . </li></ul><ul><li>These components can be correlated with the various sub divisions within the project. </li></ul><ul><li>Classification </li></ul><ul><li>Broadly speaking , they are collection of one or more products. </li></ul><ul><li>These can be loosely termed as a domain. </li></ul>
  16. 16. Classification
  17. 17. Classification Contd…
  18. 18. Product flow 1
  19. 19. Product Flow 1 Contd…
  20. 20. Product Flow 2
  21. 21. Product Flow 2 Contd…
  22. 22. Component Flow 1
  23. 23. Component Flow 1 Contd...
  24. 24. Component Flow 2
  25. 25. Component Flow 2 Contd…
  26. 26. Component Flow 2 Contd…
  27. 27. Bug Searching Prepared By : Charul Bhan
  28. 28. Search Bug
  29. 29. Search Bug Contd…
  30. 30. Search Bug Contd…
  31. 31. Search Bug Contd…
  32. 32. Bug Life Cycle Prepared By : Charul Bhan
  33. 33. Example <ul><li>Classification : Gaming </li></ul><ul><li>The Domain here considered is the ever-growing Gaming industry </li></ul><ul><li>Products: Mobile Gaming, PC Gaming </li></ul><ul><li>Above mentioned are two products of the gaming industry. Here we will look at the bug pertaining to the Mobile gaming. </li></ul><ul><li>Components: Functional , language, UI (user interface) </li></ul><ul><li>The bug will correspond to the UI component of Mobile Gaming </li></ul>
  34. 34. New Bug Main Page
  35. 35. New Bug Contd… <ul><li>QA Contact: User responsible for quality assurance of this bug </li></ul><ul><li>Deadline: This field shows the deadline for this bug. </li></ul><ul><li>Estimated Hours: This field shows the original estimated time. </li></ul>
  36. 36. New Bug Contd… <ul><li>Depends on: This field gives dependency of this bug on the bug specified. </li></ul><ul><li>Blocks: This field specifies the bug which is prevented from being fixed until this bug is fixed </li></ul><ul><li>Selecting the Commit button results into submission of bug and simultaneously an mail is send to the QA contacts of the bug. </li></ul>
  37. 37. Assigned state
  38. 38. Assigned state Contd…
  39. 39. Bug fixing
  40. 40. Bug verification
  41. 41. Summary Reports Prepared By : Charul Bhan
  42. 42. Summary Reports <ul><li>Provide information pertaining to the bugs present in the software in documented form. </li></ul><ul><li>The information can either be observed in tabular form or pictorial form. </li></ul>
  43. 43. Summary Reports Contd…
  44. 44. Tabular Report Summary Reports Contd…
  45. 45. Tabular Report Summary Reports Contd… <ul><li>Vertical axis: Component </li></ul><ul><li>Horizontal axis: Priority </li></ul>
  46. 46. Summary Reports Contd… Graphical Report
  47. 47. Summary Reports Contd…
  48. 48. Thanks