strict constant

standard, and red where it would have shrugged: the same five seconds and the same landing of real work afterwards, but a screen still asking for frames when both are done fails the step instead of recording settled: false and moving on.

The default's tolerance is for the loading spinner every app opens on; this is for the suite where a spinner in a picture is a bug. settled: false is a number in a report, and a scenario whose assertion finds the widget it wanted passes with a spinner in every frame for as long as nobody reads that number. The failure this throws captures the frame it gave up on, so the picture of the spinner is the first thing on the failed step.

Not full: that is pumpAndSettle's own loop, which throws before any real work has been given the chance to land and spends ten fake minutes deciding to. Set it per scenario (scenario('…', settle: Settle.strict)) or per folder (runScenarios(testMain, settle: Settle.strict)).