Problem Report Outline

A problem report is a means to report defects to a development team. The IEEE 829 Defect Report consists of entries made by both the tester and the developer:

  • Entries made by the tester:
  • Defect identification number.
  • Defect description.
  • Version number of the build in which the defect was identified.
  • The module in which the defect exists, or the functionality affected by the defect.
  • The title of the failed test case.
  • A statement as to whether the effect of the defect can be reproduced.
  • The test procedure or script that led to the identification of the defect (for defects that cause effects that can be reproduced.
  • Screen prints and a statement as to why the effects can't be reproduced.
  • The severity of the defect: high, medium or low.
  • The defect's priority: high, medium or low.
  • The defect's status: new or reopen.
  • The name of the tester who ran the failed test case.
  • The date of the defect report,
  • The recipient of the report.
  • The suggested fix.
  • Entries made by the developer:
  • Name of project manager or team leader.
  • Name of developer who fixed the defect.
  • The type of resolution: accepted, rejected or postponed.
  • The date the defect resolution was implemented.
  • The project manager who approved the fix.