v0.26.0 — pages that are still rendering, dialogs past the cap, and repeated clicks

This release fixes four ways a test failed on a correct page, or passed a run that never happened. Each was found running blastproof against a real budgeting app. Steps execute differently, which is why this is a minor.

A step waits for a page that is still rendering

An app that renders from data already in the browser goes network-idle before its first paint is done. A step could read the half-built page, and the model failed it with nothing done: no "Try the demo" button, only a "Set up sync" link, under concurrency: 4 (#14). A fail with nothing done now waits up to 3 s for the page to change, once per step. A changed page goes back to the model. A still page fails as before, with no extra model call. On a page that renders its button 2 s after idle, the step failed 3 runs in 3 and now passes 3 in 3.

The open dialog survives the snapshot cap

Frameworks render dialogs, menus and command palettes at the end of the page. A snapshot over max_snapshot_lines kept only the top, so the element the last action opened was the first thing dropped. On a 670-line page, the command palette was at line 606, and both of its tests failed at the default cap. A cut now keeps the open dialogs and the focused element first, and both pass. Omitted lines are marked where they were, and a step that fails on a cut snapshot names max_snapshot_lines in its reason (#162).

"Click Next until…" works

Within a step, a click that had already succeeded was always refused, so "click Next until the tour shows its last step" failed on its second click. A repeat now goes through when it directly follows itself and the page changed after the last press. Every other repeat is still refused, including a form refilled and submitted again. An onboarding tour now passes 3 in 3, with all 7 clicks (#164).

No score when nothing ran

When the provider refused the first call, or the budget ran out during sign-in, the reports and the action's score output said 100, even though the run exited 1. That run now has no score: the JUnit report omits it, the HTML report shows none, and the console says Score: none (#134).

Upgrade note: a workflow step reading outputs.score gets an empty string for that run.

Also

• A call that the run's deadline aborts is reported as the deadline, even when its timer fires a millisecond early (#159).
• The reliability table in the README was measured again on this release. On Haiku, one false FAIL in 40, in the notes test; everything else is unchanged.

Full entry in the CHANGELOG.