Commit Graph
39 Commits
Author SHA1 Message Date
Oskar Kwaśniewski 030d2102d5 fix(mcp): run handlers a run_code call left, redact spelled strings
Second review round: only code cut off by a cancel or the timeout is parked, so a handler one call left runs in the next; a string passes the ledger before it is escaped into a line; a rejection in the code's last turn fails the call; a cancel aborts the operation in flight and stops waiting for one that ignores it; names are numbered by the session; bytes, maps, and dates come back as themselves.
2026-11-21 22:35:46 +01:00
Oskar Kwaśniewski 0573dd6c59 feat(mcp): print a test line for a control found by its role alone
Closes #1825.
2026-11-21 16:48:55 +01:00
Oskar Kwaśniewski dbcbc2faac refactor(mcp): run run_code in Node on the real test objects
Drops the QuickJS sandbox, the guest prelude, and the closed grammar. The code runs in the server's process on the objects a test body gets, with a recorder that writes down each test line. run_code now has a test file's authority; SECURITY.md and AGENTS.md say so.
2026-11-21 15:21:35 +01:00
Oskar Kwaśniewski eeaf79ddd9 docs(ja): keep main's wording next to the run_code changes 2026-11-21 14:35:48 +01:00
Oskar Kwaśniewski b99a7cef8f fix(mcp): refuse host files by path from run_code fixture calls
A fixture member that reaches a host file by a path the code names, or the raw driver client, is POLICY_DENIED. A fixture call that outlasts its line limit is answered at the limit. A call that passes a function is kept in test_lines. A script of only test lines is checked against the secret policy before any line runs. run_code failures count by code in session usage, and read values past what the result shows are dropped.
2026-11-21 14:35:24 +01:00
Oskar Kwaśniewski 107eecc653 docs(security): state what run_code's fixture calls can read
A page script run through browser or device can return a configured secret in a changed form; recorded as an accepted exception in AGENTS.md, SECURITY.md and the security docs.
2026-11-21 14:35:24 +01:00
Oskar Kwaśniewski 1b2955bd3e fix(mcp): fail run_code on a failure the code never awaited
Second review: a line the code never waited on fails the call even when it settled early; fixture lines are spelled on the host and an awaited object gets a named const line; undefined stays undefined; clearTimeout ends the host wait; number and length matchers check their types; a reserved fixture name stays out of scope; non-plain arguments and expect on a fixture object are refused; attach refuses path.
2026-11-21 14:35:24 +01:00
Oskar Kwaśniewski 911a1a31e6 fix(mcp): stop unawaited run_code lines at a failure
Review fixes: lines made behind a failing one do not run and an unawaited or timer failure fails the call; listed reads are complete; messages reach the code redacted; lines share the call's deadline; expect(value) compares like the test API; isEditable alias removed; refused arguments carry INVALID_ARGUMENT; clearTimeout works.
2026-11-21 14:35:24 +01:00
Oskar Kwaśniewski 7d3559ea1b feat(mcp): run JavaScript in run_code, in a sandbox
run_code takes the body of an async function with screen, app, expect, credentials, secrets, and console in scope. The code runs in QuickJS (the run package, in a worker) with no host access. Each call it makes on the app is spelled as one test line and parsed by the same closed grammar, then run with the same secret checks, so loops, reads, and return values work while the grammar still decides what reaches the app.
2026-11-21 14:35:24 +01:00
5b61f221aa fix(core): stop launch() hosts from driving one mobile device (#2008)
* fix(core): give each launch() host a target name of its own

Every launch() host named its target after its platform and started as
worker slot 0, so every mobile host drove the agent-device session
e2e-ios-0: the session of another host, or of a runner worker on an
unnamed ios target. The mobile pool keeps a device its own session name
holds, so the host took that device and both tapped one screen.

A host's target is now <platform>-launch-<pid>-<n>. An agent's replay
cache keys to the platform, so recordings still replay on any host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(core): draw a random token per launch() host, renamed after resolution

The pid and a module counter repeated across worker threads and across
two copies of the package in one process, so two hosts could still share
a device session. A random token per host does not. The platform part is
cut to 40 characters, so a long engine name still fits in the artifact
folder name, and the target is renamed only after its config resolved,
so config errors name the target as the program wrote it. The replay
cache keys on the resolved name.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(core): leave a long platform out of a launch() host's name, and forget finished bindings

A platform cut to 40 characters could keep part of a secret the
redactor only knows whole, so a longer platform is left out of the name.
The token is 96 random bits. The mobile engine's finish now forgets the
target's bindings, so one engine reused by host after host no longer
keeps every finished host's device and daemon address.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(core): say how several launch() hosts share a machine's devices

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(core): say when appPath hosts can share a device, and test the 40-character name boundary

A host holds its device once its app opens, so two appPath-only hosts
launched back to back can bind one device. The recovery command now
takes the session name from the error, quoted, and names daemon stop.
The changeset said "the token alone" where the name is host-<token>.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(core): name a launch() host's artifact folders after its token, not its platform

An engine's platform can be a secret's value, and the folder name
core/<target>-<attempt> put it on disk under artifactsDir, where
redaction never reaches. The folders are now core/host-<token>-<attempt>.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(core): install an appPath build before opening it, and keep recovery to what the error names

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(core): pass launch() hosts to engines as hostId, keep target name

The random token no longer renames the host's target. Core hands it to
prepare, init and finish as hostId, and the mobile pool adds it to the
session name: e2e-<target>-<token>-<slot>. Fixtures, notices, errors,
provider tags and the replay cache key see the target name the program
wrote, so the cacheTarget indirection and the 40-character rule go.

* test(mobile): check a launch() host's init resumes the session its prepare warmed

The pool test now also has the host keep a device its own session holds
and runs init with the host's id: a surface whose init named the session
without hostId passed the old test and fails this one. Also moves the
SessionNamer doc comment back above its type.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mobile): hand a launch() host's device bindings over a variable of its own

With the target keeping its name, a host opened inside an `e2e run` test
inherits the run's environment, where the run already left its bindings
for a target of the same name. A host's worker without the bindings in
memory (an engine served in another process) read the run's and drove
the device the test holds. The variable's digest now includes hostId.

Also names the host form of the session in `DeviceSession.session` and
the reference's `session` default, and mirrors the session option's
comment into the ja and zh references.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mobile): fail a launch() host's close when its session stays open

A host's session name carries a random hostId, so no later host or run
takes its device back by name. finish now reports a session that will
not close, with its name, and counts one that is already gone as closed.
A run's worker and a session option keep their names and stay quiet.

Also from review: raise the @e2e-dev/core peer floor to 0.24.1, the
first release that sends hostId; bump e2e and web in the changeset and
say what a crashed host leaves behind; use pnpm dlx for agent-device in
the docs; drop a test that passed on main.

---------

Co-authored-by: michal-e2e <357875193+michal-e2e@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Oskar Kwaśniewski <oskar@okwasniewski.com>
2026-11-21 13:33:12 +00:00
Kazutoyo TokaiandClaude Opus 5.5 6fbadcb7cd docs(ja): catch up with English changes (#2032)
* docs(ja): catch up with English changes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDfGr6hZCd7ns31Y2WN

* docs(ja): keep the mcp limits sentence literal, fix the uninstallApp device note

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDfGr6hZCd7ns31Y2WN

* docs(ja): address review on the catch-up

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDfGr6hZCd7ns31Y2WN

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 13:32:17 +00:00
Kazutoyo TokaiandClaude Opus 5.5 9358e32323 docs(ja): smooth the wording on the CLI, config, and runner reference (#2027)
* docs(ja): smooth the wording on the CLI, config, and runner reference

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDfGr6hZCd7ns31Y2WN

* docs(ja): address review on the ref-runner wording

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDfGr6hZCd7ns31Y2WN

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 13:32:07 +00:00
Kazutoyo TokaiandClaude Opus 5.5 2c335e9c98 docs(ja): smooth the wording on the test API reference (#2026)
Claude-Session: https://claude.ai/code/session_01Mn9zDfGr6hZCd7ns31Y2WN

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 13:32:05 +00:00
Kazutoyo TokaiandClaude Opus 5.5 c37d375d5f docs(ja): smooth the wording on the engine authoring pages (#2025)
* docs(ja): smooth the wording on the engine authoring pages

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDfGr6hZCd7ns31Y2WN

* docs(ja): address review on the engines wording

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDfGr6hZCd7ns31Y2WN

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 13:32:03 +00:00
Łukasz LechandClaude Opus 5.5 1d28ac0fea feat(mobile): add device.isKeyboardShown() (#1893)
* feat(mobile): add device.isKeyboardShown()

Returns whether the soft keyboard is on screen from one capture: the
keyboard agent-device reports (a measured or derived frame, or a
visibility probe), else visible keyboard elements in the tree, the same
band observations hide covered nodes under. A capture that cannot answer
(no keyboard in a sparse or cut tree, or keyboard elements agent-device
rejected with no probe) fails with ENGINE_FAILURE instead of guessing.

Refs #1855

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(i18n): mirror the isKeyboardShown heading and rows in ja and zh

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(mobile): note that isKeyboardShown reads the screen as it is now

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mobile): answer isKeyboardShown only from what the capture can prove

- An unmeasurable keyboard reading answers false only for the reasons that
  say agent-device read the whole tree; a capture that could not see the
  keyboard's window fails with UNSUPPORTED_CAPABILITY.
- A rejected docked frame with no probe reads as shown: agent-device
  rejects one only for a tree that lists keyboard elements, as a keyboard
  still sliding in does on an iPhone.
- The incomplete-tree failure no longer claims a retryable flag that
  EngineError drops for ENGINE_FAILURE.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mobile): read the keyboard by one rule and answer false only on proof

Review follow-up for isKeyboardShown:

- keyboardShownIn moves to keyboard.ts and is the one rule:
  dismissKeyboard's check is keyboardShownIn === true.
- Only agent-device's `absent` (or a probe that says hidden) answers
  false. keyboard-not-observed and keyboard-visibility-probe-unsupported
  now fail with UNSUPPORTED_CAPABILITY.
- Tree answers count keyboard elements drawn on screen only, so a
  keyboard left in the tree off screen does not read as shown.
- A tree-rejected reading with no on-screen key is the keyboard moving:
  both isKeyboardShown and dismissKeyboard capture again, briefly, before
  they answer.
- The benchmark test taps the field first, since a fill on Android opens
  no input method, and polls both reads.
- The ja and zh Throws tables are translated, and the Appium guide notes
  that the call reads the screen as it is now.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(mobile): say a keyboard reading can take several captures

isKeyboardShown's JSDoc and the reference said one capture, but a
keyboard still moving is captured again. keyboardShownIn's comment now
names what it decides instead of every keyboard check (observations
report measured state only), and the unsupported message says the tree
shows no keyboard drawn on screen.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(mobile-benchmark): read the keyboard on iOS only

The Android emulator in CI draws no soft keyboard, even for a tapped
field, so isKeyboardShown polled false until it timed out. The keyboard
reads move to their own iOS-only test, and the onboarding test is back
to what main has.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mobile): start the keyboard drag above every element that says the keyboard is up

The drag's top edge came from keys alone, while isKeyboardShown also counts
the suggestion strip, so a capture that lists only the strip (a hardware
keyboard) dragged from under it. The reference example now polls the read
after dismissKeyboard, and the changeset notes the transition wait follows
the same rule.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(mobile): say the strip drag starts above the strip

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(mobile): pin the drag above the strip when keys sit under it

The strip-only test could not tell the highest keyboard element from any
of them. It now also lists the strip above the keys, with the strip holding
only text so nothing but the keyboard's top keeps the drag off it. The
drawn-keyboard predicate is one helper that keyboardBand and
keyboardElementsTop both read.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mobile): refuse a keyboard drag when nothing bounds the keyboard

A visibility probe that says the keyboard is up, with no frame and no
keyboard element on screen, left keyboardTop at the bottom of the screen, so
the drag could start on the keyboard. dismissKeyboard now fails with
UNSUPPORTED_CAPABILITY there instead of guessing. The strip test's
assertion names the failing y.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mobile): read the soft keyboard from keys, and keep each look in the budget

The suggestion strip alone, as XCTest lists it with a hardware keyboard, no
longer reads as the soft keyboard shown; it still bounds where the
dismissing drag may start, now also above a measured or derived frame. The
settle loop reserves the last capture's time along with its backoff, so a
slow capture after the drag no longer times the dismissal out. A capture
with no viewport and no window places no keyboard on screen, since the
tree's own extent holds the keyboard it is asked about.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(mobile): say expect.poll reads isKeyboardShown again after any error

A lasting UNSUPPORTED_CAPABILITY makes the poll wait out its timeout; the
docs implied only ENGINE_FAILURE was read again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 13:58:41 +01:00
Samanyu DasandClaude Opus 5.5 7a8e546e26 fix(mobile): fail toHaveScreenshot with POLICY_DENIED when a secure field can't be masked (#2014)
* test(mobile): expect a screenshot mobile withheld to be refused for masking

On mobile, a screenshot the engine cannot mask is withheld with no sign it
was ever taken, so toHaveScreenshot waits out its timeout and fails with
ASSERTION_FAILED, and the agent is told the engine captures no pixels. These
tests expect the engine to report the regions it masked (none) beside the
missing pixels, toHaveScreenshot to fail at once with POLICY_DENIED, and the
agent to read MASKING_UNPROVEN. A screenshot that was never taken, or one
withheld with every secure field masked, still keeps the matcher waiting.

Refs #1996

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mobile): fail toHaveScreenshot with POLICY_DENIED when a secure field can't be masked

When a secure node on the mobile screen has no bounds, the engine cannot
mask it, so it drops the screenshot and reports nothing else. The session
could not tell that from a screenshot that failed, and the matcher checked
for missing pixels before it checked masking, so it polled until its timeout
and failed with ASSERTION_FAILED and "the engine returned no screenshot". On
the web the same case fails at once with POLICY_DENIED, which is what the
docs and AGENTS.md promise. The agent had the same gap: it was told the
engine captures no pixels (UNSUPPORTED_CAPABILITY) instead of
MASKING_UNPROVEN.

The engine contract now lets an engine withhold a screenshot it could not
mask by reporting maskedRegionCount without pixels. The mobile engine does
so for a secure node without bounds. An image it cannot read or decode is
still no screenshot, so the matcher takes another. When the count falls
short of the secure nodes, the session marks the observation
pixelsWithheld: 'MASKING_UNPROVEN', the token the agent already uses for
unproven pixels. toHaveScreenshot fails with POLICY_DENIED on it, and the
agent passes it on. A screenshot that was never taken (the web engine
mid-navigation, a failed device capture) reports no count, so the matcher
keeps waiting for it as before.

app.screenshot() on the same screen failed with ENGINE_FAILURE (exit 3)
for the same cause. It now fails with POLICY_DENIED too, as AGENTS.md
asks for withheld pixels. An image that cannot be decoded keeps
ENGINE_FAILURE, since there is no screenshot to withhold. Failure evidence
and agent evidence screenshots catch every error, so neither changes.

Fixes #1996

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* refactor(core): decide withheld pixels once, in the session

The session now keeps pixels on an observation only when the masked regions
cover every secure node, and marks any screenshot the engine took without
that proof, sent or withheld, as `pixelsWithheld: 'MASKING_UNPROVEN'`.
`toHaveScreenshot` and the agent's `clearPixels` read that one field and no
longer check the masking themselves.

The mobile engine reports a secure node without bounds as unbounded before
it reads the image, since no image makes that screen maskable, and drops
`decodesAsPng`. `redactSecure` returns a tagged result, and the
`ENGINE_FAILURE` message for an image it cannot read says so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(core): keep fallback pixels only when their masking is proven

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(core): isolate the unproven fallback pixels case

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(mobile): withhold pixels on an unbounded screen without a screenshot

A secure field without bounds makes the screen unmaskable from the tree
alone, so the mobile engine now checks the bounds before it takes a
device screenshot. `observe` reports no regions masked and
`app.screenshot()` fails with `POLICY_DENIED`, even when the device
screenshot would have failed, and neither pays a device round trip.

Lists `POLICY_DENIED` under `app.screenshot()` in the app reference, and
says `maskedRegionCount` is reported when the harness asks for pixels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(core): name pixelFallback as a pixels request in the count contract

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(core): mark pixels withheld only for a pixels request

The session now marks an observation `MASKING_UNPROVEN` only when the
caller asked for pixels, so the engine contract needs no rule about when
an engine reports `maskedRegionCount`. The masking check on fallback
pixels runs after the bare-root check, so a malformed unavailable tree
keeps `INVALID_STATE`. Tests pin the masked count the agent passes on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(core): name pixels: true in the withheld count contract

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(mobile): pin the error category of a withheld app.screenshot()

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(core): leave fallback pixels to the engine's own masking proof

An unavailable tree is a bare root, so the session has no secure node to
count, and checking the masked-region count against zero proves nothing.
The engine that sends fallback pixels proves their masking itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 13:53:30 +01:00
Daniel PetroandOskar Kwaśniewski e88153b2f3 feat(locator): add blur for web elements (#1919)
* feat(locator): add blur for web elements

* fix(locator): declare blur against the required core version

* fix(locator): cover MathML blur and engine capabilities

* docs(locator): list blur in action references

* fix(web): require core and e2e 0.24.1 for locator actions

---------

Co-authored-by: Oskar Kwaśniewski <oskar@okwasniewski.com>
2026-11-20 15:58:39 +00:00
Samanyu DasandClaude Opus 5.5 198d25f038 feat(test): add test.fixme (#1887)
* feat(test): add test.fixme

test.fixme takes the four call shapes test.skip takes. test.fixme(title, fn)
registers a skipped test whose body never runs. test.fixme(), test.fixme(reason),
and test.fixme(condition, reason) skip the running test from a body or hook.
Both report the test skipped with cause explicit and the reason "fixme", or
"fixme: <reason>" when a reason that is not blank is given.

The runtime form shares skipRunningTest with test.skip, which now takes the
API name so every error names test.fixme(). The registration form rejects a
serial group with an API-named message, as test.skipIf and test.runIf do.

Refs #1855

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(test): say test.fixme's reason and setup error need a non-blank reason and a true condition

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(test): route test.skip(title, fn) through registrar and mirror test.fixme docs in zh

test.skip(title, fn) in a serial group now names test.skip(), as test.fixme,
test.skipIf, and test.runIf do. docs/zh, which landed on main after this
branch was cut, gets the test.fixme section, the serial-group rows, the Types
block, and the Playwright guide rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(changeset): keep the test.fixme changeset to one sentence

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* feat(report): report test.fixme with its own skip cause, fixme

A test.fixme test, registered or skipped from its body, now reports
skip.cause fixme in report-v1, beside explicit. The reason text is
unchanged. Every consumer that counted an explicit skip as one the test
gave itself counts fixme too: serial member accounting, Skipped After
Failure, the GitHub merge summary, and NO_TESTS, which says marked fixme.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(test): document the fixme skip cause, and pin the GitHub merge count

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(report): keep fixme out of --last-failed, and cover the fixme cause's other paths

A SelfSkipCause type names the causes a test gives itself, and
RUNTIME_SKIP_APIS carries each runtime skip API's cause, so a new one
cannot report half-wired. Tests now pin --last-failed leaving fixme out,
the fixme cause beside a failure that outranks it, and the explicit
fallback for a RuntimeSkip from an older copy. The docs align the
test.skip setup row and say the Playwright guide's { skip: 'fixme' }
workaround reports cause explicit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* chore(changeset): tell users to update @e2e-dev/github with e2e for the fixme cause

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(types): give test.fixme(title, fn) worker fixtures, and name it in the executed docs

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* ci: rerun checks after a flaky app-command-exit test on Node 24.8.0

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(migrate): name the serial-group exception for skip and fixme registrations

Playwright accepts test.fixme(title, fn) and test.skip(title, fn) inside a
serial describe, and e2e rejects them, so the "the same" cell names it.
Type a caught runtime skip's cause as unknown, so every reader goes through
runtimeSkipCause, and keep RuntimeSkip module-private. State the github
changeset as the symptom, and name test.fixme in the skip JSDoc.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: shorten the migrate cell, and name test.fixme in failureBeforeSkip

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: list test.fixme(title, details, body) as missing, and fix the github changeset

The PR comment never shows the executed count, so the changeset names the
merged report instead. The Playwright guide lists the details form under
the APIs e2e does not have yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs(migrate): list Playwright's skip and fixme callback forms as missing

Playwright's test.skip(callback, description) and
test.fixme(callback, description) fail collection in e2e with
COLLECTION_ERROR. The guide now lists them, with the conditional form
inside the body or platforms on the test as the workaround, in en, ja,
and zh. The ja test reference says 直列実行 for serial groups, like the
rest of that page.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(schema): put the fixme skip cause in both report-1 fixtures

The valid fixture's runtime skip, on the result and its attempt, now has
cause fixme. The invalid fixture's skip that names a filter now has cause
fixme, and a test checks that the schema rejects exactly that pair: the
rule that only a filtered skip names a filter fails at that cause, and
deleting the filter clears it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* test(test): skip as fixme after a timeout test.setTimeout raised

A test that raises its timeout from 300 ms to 10 s, waits 900 ms, and then
calls test.fixme() is reported skipped with cause fixme, on the result and
its attempt.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-20 15:30:09 +00:00
b25bb45a7d docs(ja): fix mistranslations (#1991)
* docs(ja): fix mistranslations

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): address review on mistranslations

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): keep "starts at" for headers, name the runner for onRunFinished

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Kacper Kapuściak <kapusciak.k@gmail.com>
2026-11-20 12:15:55 +00:00
Kazutoyo TokaiandClaude Opus 5.5 9e4e6d3df7 docs(ja): unify terminology (#1992)
* docs(ja): unify terminology

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): address review on terminology

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): keep 独自の for custom used in a sentence

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): use 独自の for custom in running text

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): translate location as ロケーション

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): title the tools card プロジェクトツール

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): translate redact as 秘匿 and mask as マスキング

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): translate secret redaction as 秘匿 in the Appium guide

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): call screenshot redaction マスキング

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-20 11:35:40 +00:00
Kazutoyo TokaiandClaude Opus 5.5 4d30f71647 docs(ja): catch up with English changes (#1987)
* docs(ja): catch up with English changes

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): address review on the catch-up

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

* docs(ja): note the plugin MCP server is Codex and Cursor only

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mn9zDiruYSYKYCyiEcZJPE

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-20 11:26:10 +00:00
VarshithandOskar Kwaśniewski a06b931b8d fix(web): launch Chromium with its sandbox on where it can start (#1621)
* fix(web): launch Chromium with its sandbox on by default

The web engine launched Chromium without chromiumSandbox, so Playwright added --no-sandbox to every browser process. The agent can follow the app to another origin, so a renderer exploit on a page it reaches ran unsandboxed as the user running e2e run, with the checkout, .env, and model keys in reach.

Chromium now launches with chromiumSandbox: true unless the config opts out with web({ chromiumSandbox: false }) or the run environment sets E2E_CHROMIUM_SANDBOX=0, for hosts where the sandbox cannot start (root, containers, Ubuntu 23.10+ with the AppArmor user-namespace restriction). Firefox and WebKit never receive the option. The flag resolves from the option, then the run's environment, then on; the process environment never decides a launch, per the EngineInitInfo.env contract. CI opts out explicitly because the ubuntu-2404 runners restrict unprivileged user namespaces.

Docs updated next to the no-origin-allowlist note (docs/reference/web.mdx, docs/security.mdx, SECURITY.md, skills/e2e/references/setup.md) with a .changeset entry. The smol VM's --no-sandbox is unchanged: the VM is the boundary there.

Verified: pnpm check green; web unit 354/354; web integration 379 passed with 3 known load flakes that pass in isolation; testbed CLI 6/6 fail with "Chromium sandboxing failed!" by default and 6/6 pass with the opt-out on this host.

Fixes #1613

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* docs(web): qualify chromiumSandbox coverage as local-launch-only

Cubic review on the sandbox-default PR found three doc overstatements: SECURITY.md presented the sandbox as universal while connect() and browser providers bypass launch, the skill reference omitted that E2E_CHROMIUM_SANDBOX=0 only applies when the option is omitted, and the reference page implied any container cannot run the sandbox. All three are corrected in the SECURITY note, the reference page, the option JSDoc, and both skill copies.

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* fix(web): friendly Chromium sandbox failure and unified sandbox resolution

A sandboxed launch on a host whose sandbox cannot start failed with Playwright's raw error and its full call log, which only hints at the option. acquireBrowser now catches that one failure on a local launch and throws an ENGINE_FAILURE naming both opt-outs, E2E_CHROMIUM_SANDBOX=0 and web({ chromiumSandbox: false }), with no call log and no cause chain to leak it back.

The sandbox flag resolves in one place now: resolveChromiumSandbox(configured, env) in browser-connection.ts replaces the split readChromiumSandboxFlag plus surface resolver, and the surface keeps a single field that init resolves. BrowserConnection.acquire takes an options object, so a relaunch retries with the same options. The option JSDoc shrinks to two lines pointing at the security docs.

Tests follow the restructure: the cdp-attach edits are gone (the flag never applied to attach), screenshot-caret and stalled-frame run sandboxed by default, resolved from the ambient environment so the CI opt-out still reaches a direct launch, and the workflow comments shrink to one line. New tests pin the trim and lowercase handling, the opt-out surviving a failed relaunch, and the friendly error text.

Verified: web unit 358/358 with the opt-out; a real launch on this host fails with the friendly error by default and passes with E2E_CHROMIUM_SANDBOX=0.

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* docs(web): minor bump for the sandbox default, CI opt-out, one home for the why

The sandbox default breaks Docker and Linux CI hosts, and the changeset said nothing about it: it is now a minor bump, opened as a maintainer-called release, telling users to set E2E_CHROMIUM_SANDBOX=0.

The CI docs name the opt-out where CI users find it: the GitHub Actions web workflow and the visual-testing screenshots workflow both set E2E_CHROMIUM_SANDBOX=0 on ubuntu-latest, matching this repo's own CI, with a note pointing at the security docs. The other CI pages run mobile targets only, so there is nothing to add there.

The why now lives in docs/security.mdx alone: the reference page, SECURITY.md, the option JSDoc, and the skill reference link to it instead of repeating it.

Verified: changeset-bumps, the docs check chain (anchors, MDX, examples, package managers, logos), and the skill tests all pass.

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* docs(web): qualify the Chromium sandbox opt-out as ubuntu-latest only

The visual-testing guide said Linux runners generally block the user
namespaces Chromium needs. The limitation is specific to the
ubuntu-latest runners used here, so name them and tell readers to leave
the sandbox on where it starts.

* fix(web): address review follow-ups on the Chromium sandbox default

Move the sandbox launch error out of the surface and into
BrowserConnection.launchLocal, where the browser name and the resolved
sandbox flag are already known, and drop the untested verb guard. The
error now names the environment opt-out only when the option did not set
the value, since an explicit option wins over the variable. The surface
keeps the option as a readonly field and resolves it into a private
field defaulting to true, the same pattern as headed, so startAttempt
without init no longer needs the fallback. The skill GitHub Actions
recipe runs ubuntu-latest with E2E_CHROMIUM_SANDBOX 0, the web reference
points at the new ENGINE_FAILURE instead of Playwright error text, and
the resolve helper loses its dead branches.

Web unit suite: 362/363 pass; the one failure is artifact-path, which
fails identically on the base head because a real Chromium cannot start
sandboxed in this container.

* fix(web): address re-review follow-ups on the Chromium sandbox default

Resolve the sandbox into one { enabled, fromOption } object and pass it through acquire into launchLocal, which now takes the options object instead of five positional args, so the launch and its error cannot disagree about which opt-out set the value. Add the waiter-joins-a-pending-relaunch case, where the re-acquire runs once and a flip cannot cancel out, and assert retryable is false on the friendly error. Document E2E_CHROMIUM_SANDBOX in the environment reference, point the dead [Security](/security) links at https://e2e.com/docs/security, and fix the changeset wording, since the error no longer always names both opt-outs. The acquire JSDoc now states the actual guarantee: a launch takes the value its own call passes.

Web unit suite: 364/364 pass with E2E_CHROMIUM_SANDBOX=0 (artifact-path fails without it, identically on the base head, because a real Chromium cannot start sandboxed in this container). Web typecheck clean, oxlint clean. The new waiter test fails against a flip mutant injected on the re-acquire and passes without it.

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* docs(web): mark E2E_CHROMIUM_SANDBOX as a value in the env reference

The entry was marked flag, but on this page 0 and false mean unset for flags, while 0 opts out of sandboxing here. Mark it value so readers do not apply the wrong flag semantics.

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* docs(ci): restore the timings-history section lost in the rebase

The rebase conflict resolution in docs/ci/github-actions.mdx kept only the tail of the new Cache the timings history section, dropping its heading, intro, and example, which broke the docs anchor check (docs/ci.mdx links to #cache-the-timings-history). Restored in full; the sandbox opt-out paragraph follows it unchanged.

Verified: the docs check chain passes locally (anchors, examples, package managers, logos, MDX).

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* docs(security): soften sandbox containment wording

The security page stated a renderer exploit stays contained by the
sandbox, which reads as a guarantee. Say the sandbox helps contain it
and note it does not prevent sandbox escapes or Chromium
vulnerabilities, matching the review feedback on the Chromium sandbox
default.

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* docs(security): wrap the sandbox containment sentence at 80 columns

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* fix(web): import EngineError from @e2e-dev/core/engine

browser-connection imported EngineError from e2e/engine, so loading the
web engine without the e2e package failed with ERR_MODULE_NOT_FOUND.
That broke the core-only install smoke check, which loads each engine
main entry without e2e installed. Import from @e2e-dev/core/engine
instead, like every other file in the web engine.

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* docs(security): re-wrap sandbox paragraph and soften changeset wording

Re-wrap the sandbox containment paragraph in docs/security.mdx at 80
columns so vulnerabilities; no longer sits on a line of its own, and
soften the changeset to match: the sandbox helps contain a renderer
exploit but does not prevent sandbox escapes. The changeset keeps only
the user-facing part: what changed and the two opt-outs.

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>

* fix(web): default the Chromium sandbox by platform, drop the env opt-out

On for macOS and Windows, opt-in on Linux where root, most containers
and Ubuntu 23.10+ cannot start it. The option alone decides, so CI,
the test env forwarding and the docs recipes need no opt-out.

* test(web): drop the relaunch cases the waiter test already covers

---------

Signed-off-by: Varshith Puli <pulivarshit@gmail.com>
Co-authored-by: Oskar Kwaśniewski <oskar@okwasniewski.com>
2026-11-20 11:25:39 +00:00
Karol Kulesza b180433047 feat(mobile): device.uninstallApp(id) and device.isAppInstalled(id) (#1906) 2026-11-20 13:03:34 +02:00
Parbez a5d178897a feat(test): change the running test's timeout with test.setTimeout (#1921) 2026-11-20 06:03:25 +00:00
Oskar Kwaśniewski 8eb3cc27ea fix(web,mobile): name engine handle types for inferred configs (#1976) 2026-11-19 18:09:30 +02:00
Oskar Kwaśniewski 1676981ab7 chore(mobile): bump agent-device to 0.21.40 (#1975) 2026-11-19 16:06:49 +00:00
Krzysztof Moch eddf577526 feat(reporters): build the built-in reporters on the public Reporter API (#1936)
* feat(reporters): build the built-in reporters on the public Reporter API

The built-in list, dot, json, junit, and markdown reporters now use only
the public Reporter contract: factories on e2e/reporters, printsTo for the
terminal stream a reporter prints to (one reporter per stream), live
onOutput, onStepPrompt, and onSummary hooks for any number of reporters,
and reportFiles for files the runner writes atomically. The list and dot
ids beside json print to stderr, so list,json now works as dot,json does.
@e2e-dev/html-reporter writes through reportFiles.

* docs(reporters): bring the Japanese and Chinese reporter pages up to date

Translates the reporter reference, the config reporters table, the
--reporter row, and the debugging output paragraph. In English, the name
section now says a reporter may share a built-in's name, and two lines
read less ambiguously.
2026-11-19 15:58:33 +00:00
Oskar Kwaśniewski 0e9d58ec98 feat(mcp)!: remove the run_tests tool (#1967) 2026-11-19 13:31:59 +02:00
Satyajit Sahoo 34322c5416 feat(cli): pause at screen.pause() under --watch (#1905)
Under `e2e run --watch`, a test is now paused at each `screen.pause()` on
every run, as in `e2e run`.

While a pause is shown, the keys are read by the pause prompt and not by
watch mode:

- Press Enter to resume the test.
- Press `q` to cancel that run and stay in watch mode.

`e2e run --step next` and `stop` can be used from another shell, as for a
run without `--watch`.
2026-11-19 11:15:49 +00:00
Satyajit Sahoo 4893d1dd75 feat: add screen.pause() (#1904)
With `await screen.pause()`, a test is paused at that line, with the app
open, until someone resumes it.

- In a terminal, press Enter to resume the test.
- From another shell in the same directory, run `e2e run --step next`.
  A run without a terminal is resumed this way.
- Paused time doesn't count toward the test's timeout.
- With `CI` set, the test fails with `PAUSE_IN_CI`.
- Under `--step`, a test is still paused after `n` or `a`.
- A test isn't paused in an MCP `open_session {test}` session, under
  `openHost` or `run()`, or in a core program.
- A test isn't paused under `e2e run --watch` yet.
2026-11-19 11:00:39 +00:00
Milosz JankiewiczandOskar Kwaśniewski 5e9b82e6ae feat(oauth): name the SuperGrok provider spacexsi, with spacexai and grok as aliases (#1943)
Co-authored-by: Oskar Kwaśniewski <oskar@okwasniewski.com>
2026-11-19 12:07:52 +02:00
bardropandOskar Kwaśniewski a213247170 feat(test): add test.each and test.for (#1882)
* feat(test): add test.each and test.for

* fix(test): read %i and %f titles like parseInt/parseFloat, as Vitest does

* fix(test): keep each titles on one line and spread only all-array tables

* fix(test): type unknown each rows loosely and keep only real cycles as [Circular]

An unknown row may be spread or passed whole at run time, so EachArgs
now types only the fixtures, last. %j only reads Node's circular-structure
TypeError as a cycle; a toJSON that throws names the row. Docs say %d
keeps BigInt's n suffix and shows Symbol as NaN, and that a string title
value keeps its line breaks.

* docs(test): note that %i keeps the BigInt n suffix

* fix(test): print undefined for %j of a function or Symbol, read Unicode $keys

- %j prints undefined for what JSON leaves out, as Vitest does, so a
  function's source never lands in a title
- $name and its path read Unicode identifier characters
- inline the test mode back into registrar
- docs: note that a Vitest test.each body gets no fixtures

* fix(test): read test.each fixtures from the parameter after the row

Fixtures are now set up on demand from what the body destructures (#1891).
A test.each row runs a wrapper, (fixtures) => body(...row, fixtures), so
registration read the wrapper's own parameter and refused every row with
"must destructure its first parameter". registerTest now takes the body
and the position of its fixtures parameter (the row's length when it is
spread, else 1), and fixtureNames reads that parameter.

* fix(test): keep Error rows on one line and locate rows through a helper

- An Error in a title shows as its name and message, not its stack, and
  whatever inspect still breaks is joined, so a title is always one line
- The source location reads the whole stack: the default 10 frames cut the
  test file off a row declared through a helper and a describe
- A tagged template table is a COLLECTION_ERROR instead of one test per
  template chunk
- A bound row body is told how to wrap itself with the row first
- tests: a run sets up only the fixtures a row body names; fixtureNames at
  a position
- docs, skill, changeset: a row body names its fixtures after the row

* fix(test): restore the stack limit on a throw, read only an own raw

- stackLocations puts Error.stackTraceLimit back in a finally
- Only an own raw property marks a template table
- The wrap hint for a bound row body names one argument per row item
- skill: rows are spread only when every row is an array

---------

Co-authored-by: Oskar Kwaśniewski <oskar@okwasniewski.com>
2026-11-19 08:56:16 +00:00
Asheesh Kumar 243eaa40ec fix(html-reporter): keep the previous page when a run stops before its tests (#1915)
* fix(html-reporter): keep the previous page when a run stops before its tests

writeReport never checked run.reportPath, so a run that stopped before
its tests (NO_TESTS, a config error, an app that never started) replaced
report.html with an empty page beside the previous run's report.json and
printed an HTML report row under "Report (not written)". It now returns
early with no row, as the built-in junit and markdown reporters do, and
the FinishedRun.reportPath docs say it is also absent when the run stops
before its tests.

Fixes #1897.

* docs(runner): say run()'s reportPath is also undefined when a run stops before its tests

The same field FinishedRun.reportPath documents, in reference/runner.mdx
and the ja and zh pages. The changeset is one line.
2026-11-19 02:36:26 +00:00
Oskar Kwaśniewski 9d240ac954 feat(core): report launch() sessions in the test that opens them (#1935)
A session a test opens with launch() from @e2e-dev/core was invisible to
the test's report, and a secret passed only to launch() could reach it.

- secrets: every owner of values (config, open host, open session) shares
  them through one refcounted map on globalThis; ledgers redact what is
  shared beside them without storing it
- report: a launch session's steps are mirrored into the test's recorder
  under an actor name (launch-1), with model usage and video
- lifecycle: the attempt owns hosts and sessions the test opened, cuts
  their steps when the body ends, and closes them at its end
- reporters: list, trace page, markdown, junit and html name the session
- errors a session throws no longer carry a secret in details
2026-11-18 16:37:55 +00:00
Krzysztof MochandOskar Kwaśniewski 847a09e6db feat(test)!: set fixtures up on demand, once per worker, and in beforeAll (#1891)
* feat(test): set fixtures up once per worker and pass them to beforeAll

test.extend() takes [fn, { scope: 'worker' }]: one instance per worker and
target, torn down when the worker ends. Suite hooks receive worker fixtures.
Engines can declare isolation: 'worker'; @e2e-dev/mobile does, so its device,
app, and screen reach beforeAll, afterAll, and worker fixtures.

Refs ENG-1297

* feat(e2e)!: set up fixtures on demand

A test now sets up only the test.extend() fixtures its body and its
beforeEach and afterEach hooks name in their first parameter, the fixtures
those name, and the auto ones. A suite hook sets up the worker fixtures it
names and the auto worker fixtures. Names are read from the function's
source, as Playwright and Vitest read them.

- [fn, { auto: true }] and [fn, { scope: 'worker', auto: true }] run a
  fixture nothing names.
- A fixture can name the fixtures declared beside it in the same extend()
  call. Fixtures run in declaration order, each after the ones it names.
- The attempt is resolved as one unit before the session launches: a
  fixture only an afterEach names is set up before the first beforeEach.
  An afterEach that names a fixture whose setup failed is skipped.
- Fixture rules fail as COLLECTION_ERROR with the file and line of the
  code: a parameter that is not destructured or takes a rest property, and
  a cycle, when the file is collected; a name the target lacks, a test
  fixture named by a suite hook or a worker fixture, and a fixture named
  like an engine's, at selection, for the pairs that run on that target.
- On an engine with isolation: 'worker', a suite hook or a worker fixture
  teardown that names no engine-backed fixture opens no engine attempt.

BREAKING CHANGE: a fixture nothing names no longer runs unless it is
declared with auto: true, and a test body, hook, or fixture function that
takes the whole fixture object (async (fixtures) => {}) no longer loads.

Refs ENG-1297

* refactor(core): declare core fixtures in one table

The five core fixtures (agent, app, screen, platform, session) are one
table in @e2e-dev/core: name, scope, and factory. createFixtures builds
the built-ins object through one loop over that table and the engine's
factories, every fixture a lazy accessor behind the same gate as before.

The runner's fixture pool, test.extend() validation, and launch read the
names and scopes from the table, so the name lists and the per-name scope
checks are gone. A launch session exposes the core fixtures that do not
belong to a test: app, screen, platform.

No behaviour change. app and screen were built with the attempt and are
now built on first read, like agent and the engine's fixtures.

Refs ENG-1297

* feat(e2e): extend a built-in fixture through test.extend

A test.extend() fixture named like one the test already has extends it,
by Playwright's rule: inside its function its own name is the fixture it
extends (the built-in, or an earlier fixture of that name), and tests,
hooks, and other fixtures that name it receive what it hands to use().

  base.extend({ device: async ({ device }, use) => {
    await device.setPermission('camera', 'deny');
    await use(device);
  } })

- A plain function takes the scope the extended fixture has on the
  target: device is a worker fixture on mobile, so its override runs once
  per worker and reaches beforeAll; app is a test fixture on web and a
  worker fixture on mobile. A declared scope that differs is a
  COLLECTION_ERROR naming both.
- A worker-scoped override receives what a worker fixture receives for
  that built-in, the forwarder to the attempt that is running.
- On a target without the built-in nothing fails until code that runs
  there names it; then the target has no such fixture.
- Only user code sees the override: the attempt's own built-ins, which the
  runner and the worker fixtures' forwarders read, are untouched.
- Types: the override keeps the extended fixture's type and scope, through
  an extend() overload that takes overrides without type arguments.

A fixture named like a core fixture, an engine's, or an earlier one of the
chain was refused before.

Refs ENG-1297

* docs(fixtures): name built-in fixtures and give their scope per engine

The docs now use one term, built-in fixtures, for agent, app, screen,
platform, session, and the ones an engine contributes (browser, device),
where pages said core fixtures, contributed fixtures, or engine fixtures.

The test reference gets one table with each built-in fixture's scope on
web and on mobile, and says what the scope decides: a test fixture reaches
test bodies, beforeEach, and afterEach; a worker fixture also reaches
beforeAll, afterAll, and worker fixtures. The hooks, worker fixtures, and
override sections link to it, as do the fixtures guide and the engine
pages. The Japanese and Chinese pages carry the table and the same terms.

Refs ENG-1297

* docs(ja): translate the fixture scope and on-demand changes

* docs(zh): translate the fixture scope and on-demand changes

* fix(e2e): let a worker fixture name an extended app or screen

A fixture that extends `app` or `screen` was taken for a test fixture when
its test.extend() call was checked, before any target is known. A worker
fixture declared after it that names `app` then failed at import on every
target, though the same fixture is accepted without the override and the
plan resolves both to worker scope on an engine whose state outlives a
test.

The scope of a plain function is now unresolved until a target is known,
whatever it extends, as it already was for an engine's own fixtures.

Refs ENG-1297

* fix(e2e): fail a suite hook that left an engine step running

On an engine whose state outlives a test, a beforeAll or afterAll hook, or
a worker fixture's teardown, can start a device step and not await it. The
hook's attempt then closed under the step, and its failure arrived later
as a stray rejection charged to whichever test ran then.

The suite attempt now does what a test attempt does once its body settled:
the step is failed at its call and cancelled, its outcome is awaited within
the cleanup budget, and the hook fails with STEP_NOT_AWAITED (HOOK_FAILED
for a suite hook).

The suite attempt keeps no step records, and StepRecorder dropped the
record of the step it had just opened before marking it running, so there
was nothing to abandon: a step now counts as running before the retained
window is trimmed.

Refs ENG-1297

* refactor(e2e): keep the fixtures a function names beside it

Registration parsed each test body, hook, and fixture function for the
fixtures it names, dropped the result, and left it in a WeakMap that the
planner and the pool read back with placeholder subjects. A cache miss
there would have named the wrong code and no line.

The parse result is now data: `names` on the registered test, the hook,
and the fixture definition. The planner and the pool read it, the WeakMap
and the per-function wrappers are gone, and one describeUser() gives an
error its subject. The explore test, registered by hand, parses its body
where it builds the record.

Unit tests state the names instead of generating source text for them.

Refs ENG-1297

* refactor(core): resolve built-in fixtures in one place

The core table declared the core fixtures, but what a target's built-in
fixtures are was still assembled around it: core names plus engine names in
three files, the 'engine' scope resolved in e2e through a cast into the
table, `platform` hard-coded as the one fixture that needs no attempt, and
two structural copies of the target.

core now exports builtInFixtures(target): names, scope(name),
needsAttempt(name), attemptless(name), and the unknown-fixture message,
over one BuiltInTarget. `platform` declares in the table that the target
alone decides it. launch, the planner, and the pool read from it.

DECLARED_BUILT_INS is the same view before a target is known: a scope the
engine decides is 'unresolved'. The planner takes either one, so its
no-target mode and the `target === undefined` branches through scopeOf and
read are gone. The scope of a fixture that extends `app` before a target
is known is 'unresolved' by construction.

Refs ENG-1297

* refactor(e2e): hand each function the fixtures it names

Every test body, hook, and fixture function must destructure its first
parameter, so what it reads is known before it runs. bindFixtures still
built a Proxy-gated bag for arbitrary property reads: one value in three
stores, the gate run twice (once over a faked plan), a third derivation of
scope, and an own-name shadow that re-derived what the planner had resolved.
No test code could reach the gate's throwing branches; only unit tests did,
by reading the bag directly.

The plan now records, per function, what each name it reads resolved to: a
chain fixture or a built-in. The pool hands each function a plain object
with exactly those names, the value a chain fixture handed over, or a
built-in read off the attempt when the function destructures it, so
built-ins stay lazy. An override that names itself receives the fixture it
extends because that is what its own name resolved to.

- bound.call(user) replaces user.fn(bound.fixtures); ready(user) asks
  whether every chain fixture it names was provided.
- attemptlessBuiltIns is a function from a name to a value that throws the
  reason for a built-in that needs an attempt.
- The planner runs once: it records what each fixture names, and the order
  is one declaration-order walk over that record. A second validating pass
  only reordered.

Behaviour: a bound or native function, whose parameters cannot be read, is
a COLLECTION_ERROR; it used to parse as naming nothing and still got lazy
built-ins. The docs no longer promise hooks and the body one shared object.

Refs ENG-1297

* refactor(e2e): move the suite attempt out of TargetExecutor

dispose, openSuiteHooks, and openSuiteAttempt were 177 lines of a second
attempt lifecycle inside TargetExecutor, written as closures in one method.

run/suite-attempt.ts now owns it: a SuiteAttempt class with open, acquire,
within, and close, over a SuiteAttemptHost interface the executor satisfies
(the way serial.ts borrows it through SerialHost), plus the worker
fixtures' teardown pass. It is the realm's SuiteHookSession itself, so the
executor keeps a context object and two call sites.

The three branches that built an attemptless reader with a "not available
to the <label>" error are one NoAttempt value ('isolated', 'unnamed',
'interrupted', or the launch failure) and one mapper to the message.

execute.ts: 1244 lines to 1052.

Refs ENG-1297

* refactor(e2e): share the attempt's fixture sequence

A run's attempt and an `e2e mcp` session's test each planned the test's
fixtures, bound them, entered the worker pool, set them up, ran the
beforeEach hooks and the body, filtered the afterEach hooks that can still
run, and labelled the teardowns. This PR widened that copy, and
standalone-test.ts asked the realm for the same hooks four times.

planAttemptFixtures(target, test, hooks) plans before any session exists
and returns open(), which binds the plan to the attempt: enter(), run()
for setup, hooks, and body, and cleanup() for the labelled afterEach hooks
and teardowns. Both call sites keep their own phases, budgets, and error
handling around it.

execute.ts: 1052 lines to 1031, its size on main.

Refs ENG-1297

* refactor(e2e): open the suite-hook pass without a lazy thunk

withSuiteHooks handed its work a thunk that opened the pass on first use.
Opening one does no I/O: the suite attempt launches nothing until a hook
that names an engine fixture runs. The pass is now opened up front and
closed in finally, and the `opened` slot and the `hooks()` call form go.

Refs ENG-1297

* refactor(e2e): ask the registry which hooks apply to a test

The selection-time fixture check rebuilt the scope chain of a test and
filtered the file's hooks by it, which the realm already did its own way.
registry.ts now exports scopeChain(test) and hooksFor(registration, test),
and both use them.

Refs ENG-1297

* refactor(core): move the fixture types into types/fixtures.ts

types.ts grew from 1679 to 1798 lines in this PR. The fixture scope, the
worker fixtures, and what test.extend() takes (definitions and overrides)
are one coherent group that nothing else in the file defines against, so
they move to types/fixtures.ts and types.ts re-exports them. The public
surface is the same.

types.ts: 1798 lines to 1715.

Refs ENG-1297

* refactor(core): drop the redundant override branch in FixtureDefinitions

A fixture that extends one the base already has was typed three ways: a
conditional branch inside the `Extra` map of FixtureDefinitions, the
`& FixtureOverrides` intersection, and the extend(overrides) overload.

Compiling the type tests without each in turn: the intersection types an
override written beside new fixtures with type arguments, and the overload
types an override-only call without them; both fail the tests when
removed. The conditional branch does not: with it gone the tests pass, and
a base name in `Extra` is `never` again, as it was before overrides. It is
removed, and the reference's copy of the declaration follows.

Refs ENG-1297

* refactor(e2e): split fixture errors from the parser, share hookLog

fixture-names.ts parses a parameter list, and also held FixtureUseError and
declarationSite, which format an error. They move to fixture-errors.ts.
Its identifier pattern held two raw zero-width characters; they are
written as escapes now.

hookLog and LOG_MODULE were pasted into three integration tests; they are
one helper in tests/helpers/hook-log.ts.

Refs ENG-1297

* docs(e2e): name the scope rule in the selection check's summary

The summary of assertFixtureUse still listed a chain fixture named like an
engine's as an error. Such a fixture extends the built-in now; the rule
left is a declared scope that differs from the extended fixture's.

Refs ENG-1297

* refactor(e2e): take execute.ts under 1000 lines

Two more pieces that are not the attempt's own sequence leave the file.

- Holding steps for `e2e run --step`: reading the screen a hold starts on
  and wiring AttemptHolds to the runner's hook move to step-hold.ts, beside
  the holds they configure (holdAttemptSteps, readHeldScreen).
- The result of a finished test or setup unit is a pure function of the
  pair, the verdict, the attempts, and a beforeAll failure: unitResult in
  units.ts, beside pairResult.

execute.ts: 1031 lines to 956. It was 1031 on main and 1226 at the review.

Refs ENG-1297

* test(e2e): match the not-awaited message without a step label

Main's #1880 names an unlabeled step by its api alone ("gadget.hang
finished"), where the message used to quote an empty label. The suite-hook
test's pattern required a label between the two, so it failed on the merge
with main.

* feat(e2e): an override inherits auto from the fixture it extends

A fixture that extends another and does not state `auto` now has the
extended fixture's, the way it has its scope: an override of an auto
fixture is set up for every test, and one of a built-in fixture on demand.
An `auto` that differs from the extended fixture's is a COLLECTION_ERROR
naming both, worded like the scope mismatch. This matches Playwright.

It also fixes which fixtures the plan starts from. An auto fixture was a
root by its own flag, so with an auto base and its override in one chain
the base was set up and the override skipped, while the name resolved to
the override; an override that replaced the base without naming it still
left the base running. An auto fixture is now a root only where its name
stands for it: the base runs once through the override's own name, or not
at all when the override replaces it.

Refs ENG-1297

* fix(core): name the hook or fixture that left a step running

STEP_NOT_AWAITED said "the test body returned before ..." for a step a
beforeAll, afterAll or beforeEach hook, a fixture's setup or a worker
fixture's teardown left running. The recorder now keeps the owner each
step was started under, and the runner says which code runs: the pool
for fixtures, hooks and the body, the suite attempt for suite hooks, and
a hosted session for itself.

---------

Co-authored-by: Oskar Kwaśniewski <oskar@okwasniewski.com>
2026-11-18 13:09:51 +00:00
Natasha Tran 902f044b49 feat: add a dot reporter (#1911)
* feat: add a dot reporter

* fix: flush dot output and separate list formatting

* docs: clarify buffered dot reporter output
2026-11-18 12:58:46 +00:00
Kacper K d16ad2c2d5 feat(cli): add e2e report command to open HTML reports (#1892) 2026-11-18 08:39:35 +02:00
ParbezandOskar Kwaśniewski fabb0c07fb feat(expect): take an optional message on locator expectations (#1865)
* feat(expect): take an optional message on locator expectations

* docs(expect): name expect.soft(locator, message) and scope the message to assertion failures

* feat(expect): open an ambiguous locator's error and expect(screen) failures with the message

* fix(expect): open an ambiguous locator's toHaveScreenshot error with the message

labelAmbiguous moves to expect/heading.ts and wraps the screenshot capture, so
expect(locator, message).toHaveScreenshot() labels LOCATOR_AMBIGUOUS as the
polling matchers do. Tests cover it, a screen .not and the CI no-stored path
with a message. The reference drops a sentence about step names.

* docs(expect): update the ja and zh pages for the locator message

The translations landed on main after this branch was cut, so the English edits left docs/ja and docs/zh stale and docs:check failed on the code blocks of reference/expect.mdx. Bring both languages level with the English pages, the Playwright guide rows included, and rewrap one line of the English soft assertions paragraph.

---------

Co-authored-by: Oskar Kwaśniewski <oskar@okwasniewski.com>
2026-11-17 21:30:02 +00:00
Kacper Kapuściak b369e382bb docs(ja): translate all 81 documentation pages (#1875)
* docs: add the Japanese translation

Adds docs/ja/, a Japanese page for every English docs page at the same
path, with the tab and group labels in docs/ja/navigation.json. The site
serves them at /docs/ja and gives each translated anchor its English id by
position, so check-docs-translations.ts keeps every translation's outline
equal to its English page's. The npm package keeps shipping only the
English pages.

* docs: check translated code blocks, keep docs/ja out of Context7 and the skill wording test

* docs(ja): sync with the English pages' latest changes (test.skipIf, tool schemas, star link)

* docs(ja): start with the quickstart page only

* docs(ja): translate getting-started and platform guides

* docs(ja): translate all documentation pages
2026-11-17 15:22:48 +00:00