MEPX
Chapter 6 of 10All chapters

Chapter 6 of 10

Reproducing a bug

The step people skip.

Make it happen on demand

Find the smallest reliable way to trigger the problem. Until you can cause it at will, you cannot tell whether a change fixed it or merely disturbed it.

  • Write down the exact input, environment and steps.
  • Turn the reproduction into a failing test before touching the code.

Reports are clues, not facts

A user describes what they noticed, not what happened. Ask what they expected, what they saw and when it started, then confirm it yourself.