1 / 11

Bug tracking tools

Bug tracking tools. Outline. Why need Bug Tracking tool? Life-cycle of a “bug report” Bug report attributes Bug tracking events Main tools Guidelines Public bug trackers. Why need Bug Tracking tool?. Collaborative software engineering

dominy
Download Presentation

Bug tracking tools

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. Bug tracking tools

  2. Outline • Why need Bug Tracking tool? • Life-cycle of a “bug report” • Bug report attributes • Bug tracking events • Main tools • Guidelines • Public bug trackers Software Engineering SS 07 2

  3. Why need Bug Tracking tool? • Collaborative software engineering • Software result of co-operation of many people typically at different locations • Communication is crucial • Many means available • face-to-face meetings, e-mail, phone • video-conferencing, instant messaging, Wiki • Bugs are inevitable • Software written by humans • It’s only human to errr Software Engineering SS 07 3

  4. Why need bug tracking tool? • Need to communicate about bugs • discovery / symptom / reproduction / reason / removal • Communication means inappropriate • e-mail: all parties involved? difficult to follow evolution. • phone, IM: all parties involved? might get forgotten. • Wiki: needs notification. • We need a specialized tool • able to trackhistory and evolution of bugs Software Engineering SS 07 4

  5. Life-cycle of a “bug report” I think I know what’s wrong. Que??? Updates Notifies Reports Open Assigned Open Unassigned Closed Notifies Self-assigns Fixes Notifies Oops, that’s in my code… Software Engineering SS 07 5

  6. Bug report attributes • Date: report, updates, close • Status: open, closed, deleted, assigned • Short summary • Detailed description • Severity and priority • Platform and version number • Category: GUI, installation, certain module • Reproduction: description or test-case Software Engineering SS 07 6

  7. Bug report attributes • Date: report, updates, close • Status: open, closed, deleted, assigned • Short summary • Detailed description • Severity and priority • Platform and version number • Category: GUI, installation, certain module • Reproduction: description or test-case(e.g. attaching core dump) Software Engineering SS 07 7

  8. Bug tracking events • Open, update and close report • Search among reports Software Engineering SS 07 8

  9. Main tools • How to choose? • free vs. commercial • featurism vs. ease of use • technical requirements • A comprehensive list of tools • www.software-pointers.com/en-defecttracking-tools.html • Most popular tools • Bugzilla, Mantis, GNATS, Flyspray Software Engineering SS 07 9

  10. Bug report writing guidelines • One issue per report • Make sure it is not reported yet • How to write useful bug report • Summary: short but quickly and uniquely identifies bug • Be specific: product, version, component, platform, OS include list of third party software used • Reproducible: provide least amount of steps Software Engineering SS 07 10

  11. Public bug trackers • bugzilla.mozilla.org • netbeans.org/community/issues.html • bugs.eclipse.org • bugs.debian.org Software Engineering SS 07 11

More Related