Skip to main content

Write a Defect Report Another Person Can Reproduce

Software Engineering, Testing, Cloud & DevOpsWorkbooks

By Jefferson Otonbara Imgbi

Published
8 October 2026
Last reviewed
8 October 2026
Record the environment, steps, expected result and actual result. Download a workbook for turning an unclear fault report into useful evidence.
Image
A magnifying glass examining a misaligned module beside sequence cards and an evidence folder.

Describe the observed fault

A defect report should explain what happened without guessing the cause. Use a concise title that distinguishes the condition from other issues. Identify the application area and version or environment where the problem was observed.

In the fictional example, the form returns an error after a valid practice selection. The report should state the input and message rather than assuming the database or a particular developer caused the fault.

Provide the starting state and steps

Explain what the tester needs before following the steps. List the actions in order and record any relevant filter, account role or configuration. Include only information another authorised person needs to reproduce the condition.

Use fictional values. If a screenshot is needed for operational work, remove inappropriate personal information and keep evidence in the authorised location. Do not paste credentials or private customer records into a public report.

Separate expected and actual results

State what the requirement says should happen and what was observed. Explain whether the fault happened once, repeatedly or only under a known condition. Keep uncertainty visible when reproduction has not yet been confirmed.

A screenshot may support the report, but should not replace the steps or explanation. Where possible, note the time and relevant system version so the team can connect the report to authorised diagnostic information.

Support the next investigation

Record the effect on the user and relevant work, without inventing severity. Follow the team’s approach for prioritisation. Add a next action or question that helps the person investigating the fault.

Download the workbook and turn the fictional statement the form is broken into a reproducible report. Ask a second person to follow it in a practice environment. Update the record if their observation differs.

Source and practice note

GitHub documentation provides context for communicating about proposed changes. The defect-report structure is original RDE practice material. Examples and exercises are original RDE material using fictional situations.

Read the official guidance

Cover image: AI-generated illustrative scene created specifically for this resource.

Download and complete the exercise

Read or print the PDF

Download the editable Word document

Printable PDF and editable Word document. Version 2.0, 8 October 2026. Personal and internal organisational adaptation permitted with Jefferson Otonbara Imgbi author credit retained.

Media and downloads

Write a Defect Report Another Person Can Reproduce (PDF)

Document
defect-report.pdf (57.67 KB)

Write a Defect Report Another Person Can Reproduce (DOCX)

Document
defect-report.docx (37.67 KB)

Related resources

Explore related RDE learning