1 / 8

Bug Tracking CSC 4700 Software Engineering

Bug Tracking CSC 4700 Software Engineering. What is Bug Tracking. Maintain a list of bugs in software Also maintain a list of features and tasks to be done Assign responsibility for each bug, feature & task Organize the work to be done Break up the work into “releases” or other deadlines.

kimama
Download Presentation

Bug Tracking CSC 4700 Software Engineering

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 CSC 4700 Software Engineering CSC 4700

  2. What is Bug Tracking • Maintain a list of bugs in software • Also maintain a list of features and tasks to be done • Assign responsibility for each bug, feature & task • Organize the work to be done • Break up the work into “releases” or other deadlines CSC 4700

  3. Good Bug Report • Steps to reproduce • What you expected to see • What you saw instead CSC 4700

  4. Bug Life Cycle CSC 4700

  5. A Bug’s Life • 1) New: When QA files new bug. • 2) Deferred: If the bug is not related to current build or can not be fixed in this release or bug is not important to fix immediately then the project manager can set the bug status as deferred. • 3) Assigned: ‘Assigned to’ field is set by project lead or manager and assigns bug to developer. CSC 4700

  6. A Bug’s Life • 4) Resolved/Fixed: Necessary code changes done, verified, bug status set as ‘Fixed’ and the bug is passed to testing team. • 5) Could not reproduce: Developer is not able to reproduce the bug, markes as CNR. QA needs action to check if bug is reproduced and can assign to developer with detailed reproducing steps. • 6) Need more information: If bug reproduce steps are not clear, mark it as “Need more information’. QA then needs to provide clearer description of steps. CSC 4700

  7. A Bug’s Life • 7) Reopen: If QA is not satisfy with the fix and if bug is still reproducible even after fix then QA can mark it as ‘Reopen’ so that developer can take appropriate action. • 8 ) Closed: If bug is verified by the QA team and if the fix is ok and problem is solved then QA can mark bug as ‘Closed’. • 9) Rejected/Invalid: Some times developer or team lead can mark the bug as Rejected or invalid if the system is working according to specifications and bug is just due to some misinterpretation. CSC 4700

  8. What’s it good for? • Works great for large teams – communication! • For small teams, good organizational tool even if everybody knows what is going on anyway • Great for planning releases and other deadlines • Also is good documentation for work being done – creates an automatic “paper trail” CSC 4700

More Related