Skip to content

Upstream: mobile bounds reads by operation budget with last-read grace (#1464) #869

Closed

Description

@kblok

Upstream commit 57f9ed9 (e2e-inc/e2e#1464): snapshots and screenshots run within the call's timeout (ACTION_FAILED instead of hanging to the test timeout); locator.waitFor, expect, toHaveScreenshot give their last snapshot grace up to the slowest one so far; OPERATION_TIMEOUT near the deadline is judged against the slowest completed read. Touches internal/time.ts, locator/engine.ts, locator/screen.ts, expect/async.ts, expect/screenshot*.ts, engine/contract.ts (OperationContext.timeoutMs doc), packages/mobile/src/{surface,support,engine,device}.ts. Tests: time.test.ts, locator-engine.test.ts, locator-wait-for.test.ts, screenshot-assertions.test.ts, mobile engine.test.ts, support.test.ts.

Port equivalents: src/E2E/Internal/Time.cs, locator engine, src/E2E.Mobile/DeviceSession.cs (see #634). Docs: docs/mobile.mdx, docs/reference/engine.mdx.

Activity

  1. kblok commented on Oct 31, 2026

    @kblok
    MemberAuthor

    An agent is working on this.

  2. kblok commented on Nov 2, 2026

    @kblok
    MemberAuthor

    Delivered by #893 (read windows, last-read grace, mobile read budget, lateAction for node actions) and #909 (observe and screenshots with a timeout, viewport probe). The one upstream it left, the positioned tap past the deadline, needs performWithin and tap position; it is already listed in #861.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions