• LoggingBugReports

Goal: Testers log clear bug reports that make developers happy.

Simple outline:

• Which bug report titles do you like?

  • Why do we log bug reports?

  • How do our bug report titles affect our credibility?

• Convert bad titles to good ones

  • Enough information for prioritization

  • As short as possible but no shorter

  • Base it on user impact

• Which bug reports do you like?

  • What is the lifecycle of a bug report?

  • For each step, which parts of the bug report support that step? Project, Issue Type, Summary, Priority, Component, Affects Version, Fix Version, Environment, Description/Steps to Reproduce

  • Why is tact so important?

  • Bug etiquette: my observations, no shouting, no value statements, explain problem rather than suggesting solution

  • One bug per report

• Take this bug report and see how long it takes you to reproduce the problem.

  • How would you improve it?

  • What would you do if you couldn't reproduce the problem/there wasn't enough info? (Invalid bugs)

  • In what ways can a bug be invalid? Why is the validity of the bug so important?

  • Additional info: screenshot, stack trace, log file

  • Minimal steps to reproduce

  • Actual vs expected behavior

• Build a short list of criteria by which to evaluate bug reports.
  • ?
• Homework: Choose a bug that you have logged, evaluate it, improve it.

  • Your thoughts? Report them next time.

• Testing is questioning. What do you question about the material today?

Sample bug report titles:

• Export/replace error
• Compare Versions confusing message
• Deleting fails
• Handle arrows correctly for rectangular images
• Find and repace doesn't always work
• Error is thrown when you clicking on an image after adding it
• Print Preview for Pathology Intro fails if the document contains a table.
• Double-clicking on image in Storyboard doesn't open the image up for editing
• Not all items in a table are picked up by Spell Check

Not covered:

• When to log a bug vs just showing it to someone.
• Bugs that are difficult to reproduce.
• Editing someone else's bug.
• Closing bugs.
• Duplicates.
• Too Many Bug Reports. (Ca we use a FAQ/Known Issues/Frequently Reported Bugs page?)
• Enhancement Requests vs Bug Reports.