1 / 34

CEN 4072 Software Testing

This presentation explores the process of tracking software problems, including problem reporting, management, and resolution. It covers the life cycle of a problem, the details to include in problem reports, bug tracking tools, and effective problem reporting techniques.

perrymanl
Download Presentation

CEN 4072 Software Testing

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. CEN 4072 Software Testing PPT2: Tracking the problem PPT and video are due: no later than September 13, 5:00 PM Submit to: lpiegl@gmail.com This template file is just an outline of the presentation that you need to complete. Additional pages will be necessary to fully explore the topic above. Each page should contain adequate text as well as illustrations. You are free to use all publicly available information (text as well as graphics) as long as the sources are properly acknowledged.

  2. Team members’ contributions Member [name]: Member [name]: Member [name]: Member [name]:

  3. What is a problem? Content outline: • Problem with respect to program runs • Examples

  4. What is a problem? Content outline: • The life cycle of a problem • The view of users and vendors

  5. Problem reports Content outline: • What is a problem report? • Definition and examples

  6. Problem reports Content outline: • What to report? • Examples of good a bad reports

  7. Bugs and product release Content outline: • Details of product release related to bug reports

  8. Bugs and operating environments Content outline: • Details of operating environments related to bug reports

  9. Bugs and system resources Content outline: • Details of system resources related to bug reports

  10. Bugs and problem history Content outline: • Details of problem history related to bug reports

  11. Bugs and expected behavior Content outline: • Details of expected behavior related to bug reports

  12. Bugs and observed behavior Content outline: • Details of observed behavior related to bug reports

  13. Managing problems Content outline: • Problem file

  14. Managing problems Content outline: • Problem data base

  15. Bugzilla problem data base Content outline: • Description of how Bugzilla handles the problem life cycle

  16. Problems: severity Content outline: • Details of problem severity

  17. Problems: priority Content outline: • Details of problem priority

  18. Problems: identity Content outline: • Details of problem identity

  19. Problems: notification Content outline: • Details of problem notification

  20. The problem life cycle Content outline: • Stages of the life cycle: • Unconfirmed • New • Assigned • Resolved • Verified • Closed • Reopened

  21. Unconfirmed problem Content outline: • What is an unconfirmed problem?

  22. New problem Content outline: • What is a new problem?

  23. Assigned problem Content outline: • What is an assigned problem?

  24. Problem resolution types Content outline: • Available resolutions to reported problems

  25. Resolved problem Content outline: • What is a resolved problem?

  26. Verified problem Content outline: • What is a verified problem?

  27. Closed and reopened problem Content outline: • What is a closed and reopened problem?

  28. The charge of the Software Change Control Board (SCCB) Content outline: • Problem management via the SCCB

  29. Problem driven development Content outline: • Software as a problem driven development process

  30. Managing the clutter of problem reports Content outline: • Manage a myriad of problem reports to avoid duplicates

  31. Problem fixes and releases Content outline: • How to fix a problem in the presence of many releases?

  32. Problems and tests Content outline: • How to handle failed tests as problems?

  33. Effective problem reports Content outline: • What are the characteristics of effective problem reports?

  34. Tools for bug tracking Content outline: • BUGZILLA • PHPBUGTRACKER • ISSUETRACKER • TRAC • SOURCEFORGE • GFORGE • Others you may find interesting

More Related