Bug report transcription typing practice
Copy reproducible issue notes with steps, expected behaviour and observed behaviour. Use a fictional interface instead of a live bug tracker.
Preview this exercise · 22 words · 131 characters
Title: Sample title is clipped. Steps: open Preview > Cards. Expected: the full title is visible. Actual: the final word is hidden.
Type the displayed passage in order. Backspace corrects the last character. Paste is disabled. Escape pauses. Control or Command plus Enter restarts. Leaving the input pauses the timer.
How to practise bug report transcription
Read the expected and actual sections carefully; they describe different outcomes. This exercise does not send a report or diagnose your device. The sample steps are ordinary text, and symbols such as > represent a navigation path rather than an action performed by the page.
What to check after a run
Check that the two outcomes were not swapped. Preserve the version label and the order of the reproduction steps.
Read the three original exercises
Preview the exact targets before choosing a run. Counts include spaces and punctuation after whitespace normalisation.
1. Find the pattern
Title: Sample title is clipped. Steps: open Preview > Cards. Expected: the full title is visible. Actual: the final word is hidden.
2. Connect the movement
Environment: training layout, version 0.4. Step 1: open the example card. Step 2: choose the narrow view. Step 3: read the caption. Actual result: the caption overlaps the border.
3. Apply it in context
The fictional report describes a filter that keeps an old label after clearing the search. Expected behaviour: all sample cards return and the filter label resets. Observed behaviour: the cards return but the label still says Saved. Copy both observations without changing the description into a proposed fix.
Original practice lesson added 26 October 2026. Educational transcription practice; no professional assessment or qualification.