An Android UI test times out. Maestro reports that an element is missing. A screenshot shows a blank or half-rendered screen.

It is tempting to fix the selector, increase the timeout, and rerun the test.

But those are often secondary symptoms. The application may have crashed several events earlier.

This article uses a synthetic UK weather forecast application to show how I separate the first actionable failure from the noise that follows it.

The failure