html5-img
1 / 25

Defect Tracking & Bugzilla

Matthew Aaron & Constantina Kacavas. Defect Tracking & Bugzilla. Defect Tracking. What defect tracking is. Defect tracking (also known as bug tracking) is a process of monitoring defects in a program.

prince
Télécharger la présentation

Defect Tracking & Bugzilla

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Matthew Aaron & Constantina Kacavas Defect Tracking & Bugzilla

  2. Defect Tracking

  3. What defect tracking is • Defect tracking (also known as bug tracking) is a process of monitoring defects in a program. • Defect tracking software utilizes a database to store information on all bugs that have been found, including: • what the bug does, • what was supposed to happen, • steps to reproduce the bug, • the current status of the bug.

  4. Why it’s important • A database can keep track of many more bugs than a human can. • Bug tracking software generally allows bugs to be searched and sorted by factors such as severity and complexity. • Anyone working on the program can check, edit, or comment on any issue.

  5. List of bug tracking tools • Bugzilla • Mantis • Trac • Redmine • Request Tracker • FogBugz • Axosoft

  6. Bugzilla

  7. Bugzilla helps users to: • Track bugs and code changes • Communicate with teammates • Submit and review patches • Manage quality assurance (QA)

  8. Benefits • Improve communication • Increase product quality • Improve customer satisfaction • Ensure accountability • Increase productivity • Bugzilla can adapt to multiple situations • Under active development • Constantly being put to the test by the Mozilla Foundation • Supported by a dedicated team • Has countless features that most expensive solutions lack • Trusted by world leaders in technology • Can be installed on many operating systems, including Windows, Mac and Linux

  9. Features • Despite being "free", Bugzilla has many features its expensive counterparts lack • Optimized database structure for increased performance and scalability • Excellent security to protect confidentiality • Advanced query tool that can remember your searches • Integrated e-mail capabilities • Editable user profiles and comprehensive e-mail preferences • Comprehensive permissions system • Proven under fire as Mozilla's bug tracking system

  10. Uses of Bugzilla • Systems administration • Deployment management • Chip design and development problem tracking • Software and hardware bug tracking • IT support queues

  11. Companies that use Bugzilla • Free software projects: • Mozilla • Linux Kernel • Gnome • KDE • Apache Project • Open Office • Eclipse • Linux Distributions • Red Hat • Mandriva • Gentoo • Novell • NASA • Facebook • Yahoo! • The New York Times • Nokia • Akamai • And many more – there are at least 1,268 in all

  12. How to use a Bugzilla

  13. Visit landfill.bugzilla.org • Landfill is a Bugzilla installation designed for testing Bugzilla

  14. Choose a test installation • This demonstration uses Bugzilla 4.4 Branch

  15. Create an account • Click “Open a new Bugzilla account” • Enter your e-mail address • You’ll get an e-mail asking you to confirm your e-mail address; do that and create your username and password

  16. Example of a bug

  17. Product and Component • Bugs are categorized according to Product and Component • Landfill has some examples: • Mozilla’s actual Bugzilla installation has Bugzilla itself as a Product with Administration, Email, Installation, User Accounts, etc. as Components

  18. Status and Resolution • The current state of the bug • Possible statuses: • UNCONFIRMED • CONFIRMED • IN_PROGRESS • RESOLVED • VERIFIED • If a bug is RESOLVED or VERIFIED, the resolution will be: • FIXED • INVALID • WONTFIX • DUPLICATE • WORKSFORME

  19. Example life cycle of a bug

  20. Other fields • Assigned To • Summary • Platform and OS • Version • Priority • Severity • Reporter • CC list • Attachments • Additional Comments • Specific installations may also have their own fields

  21. Search for bugs

  22. Filing a Bug • Click “File a Bug” on the main page or “New” on the page header/footer • Select product

  23. Filing a Bug, continued

  24. Filing a Bug

  25. References • http://www.bugzilla.org/(especially http://www.bugzilla.org/docs/4.4/en/html/index.html) • http://www.axosoft.com/ • http://www.mantisbt.org/ • http://www.fogcreek.com/fogbugz/ • http://www.thegeekstuff.com/2010/08/bug-tracking-system/ • http://www.techopedia.com/definition/25910/bug-tracking • http://www.bug-tracking.info/bug-tracking-software.php • http://www.joelonsoftware.com/articles/fog0000000029.html

More Related