1. Home
  2. Flashcards
  3. Preview

Issue Tracking

  1. Use of bug reports
    Convince a developer to spend time on your problem or feature idea
  2. People who use bug reports
    • Testers
    • Managers
    • Users
    • Developers
    • Other
  3. Bug lifecycle
    • Bug identified
    • Bug report filed
    • Bug triaged (prioritized)
    • Developer fixes bug
    • Tester checks fix
    • Bug report updated
  4. Roles of bug triager
    • Fixes very simple bugs
    • Estimates time to fix bugs
    • Gets management approval for fix
    • Recommends deferring
    • Argues that it is not a defect
  5. Roles of project manager
    Prioritize and possibly reassign reports
  6. Roles of project team
    Reviews deferred defects and reprioritizes them
  7. Roles of test group
    • Retests defects that have been marked as resolved.
    • Close report or add new information for developers.
  8. Key points in a good bug report
    • 1. Steps to reproduce
    • 2. Expected behaviour
    • 3. Actual behaviour
  9. Bug tracking a guidelines
    • Reduce reproduction steps to as few as possible
    • Only person to close report is the one that opened it
    • Keep track of versions for testing
    • Only accept reports in a database
    • Use database to track tasks, requests and improvements
    • Limit fields in database to only those necessary
    • Tie commits to version control to relevant reports
  10. Benefits of bug tracking by email
    Very few, a database should be used instead
  11. Types of bug tracking software
    • Text file
    • Spreadsheet
    • Database
  12. Team size for a text file bug tracking system
    Two people or less
  13. Team size for a spreadsheet bug tracking system
    Small
  14. Team size for a database bug tracking system
    Small to large
Author
Ant
ID
353587
Card Set
Issue Tracking
Description
issue
Updated

  1. Home
  2. Flashcards
  3. Preview