Test the task, not only the screen
A critical journey connects the states a person must move through to complete a task. It reveals focus loss, inaccessible validation, unexpected context changes and blocked recovery paths that isolated checks can miss.
Record interaction conditions
Journey evidence should identify the input method, viewport, browser, account state and step where the barrier appears. Desktop keyboard and mobile touch behaviour may differ, so both need explicit coverage when they are in scope.
Retest the original route
A component fix is not complete until the original task can be repeated under the recorded conditions. Retesting the journey checks both the barrier and the surrounding regression risk.