Stage 2 · Lesson 5 of 8

Bug reports that get fixed

A is only useful if someone can make the problem happen again quickly. Give it a specific title that names the symptom and when it happens. Then add numbered steps from a known starting point, and the expected and actual results.

Add the environment: build, browser, device and account. Finish with evidence, such as a screenshot, a short video, the failing network response or a line from the log. Report one problem per bug.

Remove steps until you find the shortest path that still shows the problem. Search for duplicates first. Mozilla's bug writing guidelines are a good model.

Common trapa report titled "Checkout broken" with no steps, which gets closed as "cannot reproduce" and wastes everyone's time.

A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock

Resources for this stage

Start with

GuideFree
ISTQB Certified Tester Foundation Level (CTFL) v4.0
ISTQB · Beginner
Chapter 4 of the free syllabus covers partitions, boundaries, decision tables and state transitions with worked examples

Practise

The Internet (practice site for test automation)
Small pages with dynamic content, broken images and tricky forms to explore and write bug reports on
Restful-booker
Deliberately buggy booking API; test it by hand in Postman and report what you find

Keep handy

Ministry of Testing
The largest testing community: free Club forum and articles on exploratory testing, charters and bug advocacy

Also worth your time

Bug Writing Guidelines (opens in a new tab)Read
A plain, proven checklist for titles, steps and expected results from one of the largest open bug trackers