verifying-web-flows

Drive the flow with browser actions like navigate, click, and type, then assert the expected end state with assert_url, assert_visible, assert_text, assert_hidden, or assert_count. Each assertion auto-waits up to its timeout and fails the run if the expectation is unmet.

assert_visible checks that an element appears on the page, while assert_text checks that an element contains an expected substring (case-sensitive by default). Pass exact: true to assert_text for an exact trimmed-innerText match.

Since v1.4.0, assert_url requires at least one of contains or pattern; a call with neither is rejected because it would verify nothing. Older tests that relied on a bare assert_url were passing vacuously and will now go red.

Selector-based assertions return a self-healing block with the element's recorded fingerprint and up to 5 ranked candidate replacements, plus a failure-context bundle with current URL, title, viewport, recent console and network errors, and a screenshot. A failure is the answer — do not retry to force a pass.

Yes. Launch the browser with storage_state_path pointing to a saved session file so the flow starts already authenticated, rather than re-driving the login. Check the failure block's current URL first — if it is /login, the session expired and the verdict is inconclusive, not a failed flow.