You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Translate the engine error of every fixture call, not only Browser steps #1120
Upstream's fixture runtime (translated(call, body) in packages/e2e/src/run/fixture-recording.ts, e2e-inc/e2e#1505bdf769bc270061b93f11847c204a9d40de737bc4) maps the engine error of every fixture call onto the runner taxonomy, with in <api> <label> as the suffix. PR #1119 does this only for Browser steps (Browser.Translated).
Left to do:
App steps and every other fixture step (Fixtures.csRunStepAsync) still throw the raw EngineException, with no ACTION_FAILED mapping and no in app.open suffix.
Browser.OnDialogAsync, WaitForDownloadAsync and WaitForDownloadsAsync call Require() before RunStepAsync, so a missing capability there is a raw EngineException and not a ConfigurationException, unlike GotoAsync.
Check with upstream whether a caller's cancel (CANCELLED from the engine) should stay a cancel here; upstream maps it to operation cancelled.
Activity