@qawolf/cli 2.1.0 → 2.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -151,7 +151,7 @@ that `url`; never guess a route and never send a repository link in its place.
151
151
  | `qawolf environment create` | write | Create an environment on the caller's team and return it in the environment.get shape. This can also create a branch on the team's connected Git provider. |
152
152
  | `qawolf environment deleteVariable` | write | Remove one environment variable by name. Succeeds whether or not the variable existed. |
153
153
  | `qawolf environment find` | read | List the team's environments, newest first. |
154
- | `qawolf environment get` | read | Read a single environment's name, kind, standing run health, flow-code branch and reconciliation state, run concurrency limit, and termination state. If flowCodeBranch exists, use its syncStatus for Git reconciliation and read lastSyncedCommitHash only when syncStatus is reconciled. |
154
+ | `qawolf environment get` | read | Read a single environment's name, kind, release readiness status, flow-code branch and reconciliation state, run concurrency limit, and termination state. If flowCodeBranch exists, use its syncStatus for Git reconciliation and read lastSyncedCommitHash only when syncStatus is reconciled. |
155
155
  | `qawolf environment getVariable` | read | Read the values of named environment variables in one call. Values are secrets. Names that do not exist go to missingNames and do not fail the call. |
156
156
  | `qawolf environment listVariableNames` | read | Use this to answer which QA Wolf environment variables are available to test code. Returns names only; values never leave the server. |
157
157
  | `qawolf environment promote` | write | Declare a preview environment's work accepted, typically when its pull request merges: its flow changes are promoted into its base environment and the environment is terminated once they land. Returns the promotion in pending; poll promotion.get to learn how it settled. Calling again while a promotion is open returns that promotion. A conflict settles the promotion conflicted and cancels the environment's in-progress runs; promotion.get names the conflicting paths. Use environment.terminate instead when the work is abandoned. |
@@ -159,7 +159,7 @@ that `url`; never guess a route and never send a repository link in its place.
159
159
  | `qawolf environment terminate` | write | Terminate a preview environment, typically when its pull request closes without merging: its flow changes are not promoted into its base. Returns the environment, now terminated. A terminated environment cannot be terminated again. Use environment.promote instead when the work is accepted. |
160
160
  | `qawolf environment update` | write | Update an environment owned by the caller's team and return it in the environment.get shape. Omitted fields remain unchanged. |
161
161
  | `qawolf file requestDownload` | read | Get a URL for reading a file out of the caller's team storage. Answers 404 when nothing is stored at that path. |
162
- | `qawolf file requestUpload` | write | Get a URL to put a file into team storage: a spreadsheet of journeys, anything too large to paste. PUT with the returned contentType, then name the path in filePaths. |
162
+ | `qawolf file requestUpload` | write | Get a URL to put a file into team storage: a spreadsheet of journeys, anything too large to paste. PUT with the returned contentType, then name the returned filePath in filePaths. |
163
163
  | `qawolf flow addTag` | write | Assign an existing tag to the selected flows. Create tags with tag.create. Flows that already carry the tag are reported in skippedFlows. |
164
164
  | `qawolf flow getHistory` | read | List one flow's results across runs in an environment, newest first, with status, attempts, duration, and diagnosis. Use it to spot flakiness, failure streaks, and duration trends. |
165
165
  | `qawolf flow removeTag` | write | Remove a tag from the selected flows. Succeeds whether or not each flow carried the tag; the flows that did not are reported in skippedFlows. |
@@ -173,12 +173,12 @@ that `url`; never guess a route and never send a repository link in its place.
173
173
  | `qawolf install browsers` | local | Install Playwright browsers used by the project's web flows |
174
174
  | `qawolf install clear` | local | Remove the managed runtime cache (all installed runtime versions) |
175
175
  | `qawolf investigation get` | read | Read what the QA Wolf AI investigating a run has concluded: one finding per cause of its failures, with the question waiting for a person and any answer or dispute the investigation hasn't acted on yet. A run that automatic investigation does not cover answers status "not-enabled". |
176
- | `qawolf issue addFlows` | write | Add flows to a coverage request owned by the caller's team. Flows already covered stay covered. Bug and maintenance reports link to flows through the runs that reproduce them; use run.diagnose to record one. |
177
- | `qawolf issue create` | write | Create a bug report, maintenance report, or coverage request issue for the caller's team. A user can create a maintenance report only when they can see the workspace's maintenance reports; a team or organization API key credits it to the workspace's automation user. Link its failed flows afterwards with run.diagnose. |
178
- | `qawolf issue find` | read | List the team's bug reports, maintenance reports, or coverage requests, newest first. |
176
+ | `qawolf issue addFlows` | write | Add flows to a coverage request owned by the caller's team. Flows already covered stay covered. Bug reports and blockers link to flows through the runs that reproduce them; use run.diagnose to record one. |
177
+ | `qawolf issue create` | write | Create a bug report, blocker (issue type `maintenance`), or coverage request issue for the caller's team. A user can create a blocker only when they can see the workspace's blockers; a team or organization API key credits it to the workspace's automation user. Link its failed flows afterwards with run.diagnose. |
178
+ | `qawolf issue find` | read | List the team's bug reports, blockers, or coverage requests, newest first. |
179
179
  | `qawolf issue get` | read | Get an issue by id. |
180
180
  | `qawolf issue listActivity` | read | List an issue's activity, oldest first: creation, status and priority changes, and the flows that started or stopped reproducing it. Use it to measure time to fix or to find issues that came back. |
181
- | `qawolf issue removeFlows` | write | Remove flows from a coverage request or remove bug/maintenance reproductions in an environment. Unlinked flows are left alone. Reports auto-close when no active reproductions remain and auto-close is enabled. For reports, omit environmentId only when each selected flow is linked in at most one environment. |
181
+ | `qawolf issue removeFlows` | write | Remove flows from a coverage request or remove bug report or blocker reproductions in an environment. Unlinked flows are left alone. Reports auto-close when no active reproductions remain and auto-close is enabled. For reports, omit environmentId only when each selected flow is linked in at most one environment. |
182
182
  | `qawolf issue update` | write | Update an issue owned by the caller's team. Omitted fields remain unchanged. |
183
183
  | `qawolf legacyTrigger find` | read | List a workspace's legacy per-environment triggers; trigger.find lists the current ones. For migration only; it goes when legacy triggers go. adaptiveFlowSelection becomes a generativeSuite action, which takes no tags. |
184
184
  | `qawolf legacyTrigger pause` | write | Pause one legacy trigger, the older per-environment kind, so it stops firing; use trigger.pause for a current one. Its copies in pull request environments pause too. For migration only; it goes when legacy triggers go. |
@@ -188,12 +188,12 @@ that `url`; never guess a route and never send a repository link in its place.
188
188
  | `qawolf promotion resolve` | write | Submit the resolution of a conflicted promotion: the full resolved contents of every conflicting path to keep, and every conflicting path to delete. Together they must cover exactly the paths in the promotion's conflict, and both commit hashes must match the conflict's; if a branch moved since, the call is refused as stale-conflict and promotion.get has the current conflict. Returns the promotion in resolving; poll promotion.get until it is promoted, or conflicted again if the branches moved while it applied. |
189
189
  | `qawolf run acceptScreenshotBaseline` | write | Make the new screenshot of a failed screenshot comparison the baseline, so later runs compare with it. Use it only when the difference is an intended change of the app, not a bug, noise, or a page that was not ready. Every later run of every environment of the workspace compares with the new baseline. Refuses without changing anything when the baseline changed since the run. |
190
190
  | `qawolf run create` | write | Create a run for the selected flows and/or tags in an environment. |
191
- | `qawolf run diagnose` | write | Diagnose failed flows in a run as reproductions of a bug or maintenance report owned by the caller's team. The issue's type selects the diagnosis. Each flow must have failed in the run. A flow that is already diagnosed in the run moves to this issue, and may stay linked to other open reports. The diagnosis appears on the run, and the reproduction appears under the issue's reproductions. Coverage requests cannot be diagnosed; use issue.addFlows to cover flows instead. |
191
+ | `qawolf run diagnose` | write | Link failed flows in a run to an existing bug report or blocker owned by the caller's team, recording them as its reproductions. It does not explain why a run failed; read investigation.get or attempt.get for that. The issue's type selects the diagnosis. Each flow must have failed in the run. A flow that is already diagnosed in the run moves to this issue, and may stay linked to other open reports. The diagnosis appears on the run, and the reproduction appears under the issue's reproductions. Coverage requests cannot be diagnosed; use issue.addFlows to cover flows instead. |
192
192
  | `qawolf run find` | read | List an environment's recent runs, newest first, including failed-attempt discovery metadata. |
193
193
  | `qawolf run get` | read | Get a run's status, per-flow results, links, and how many of its bugs are blocking. |
194
194
  | `qawolf run listScreenshotComparisons` | read | List the screenshot comparisons that failed a run's flows, with the expected, actual and diff images of each. Only comparisons that caused a failure are listed: a screenshot that differs within tolerance, or that differs on a line that did not fail, is left out. Each comparison tells whether its baseline changed since the run and whether the baseline still passes in other environments. The image URLs expire after a few minutes; fetch the preview URLs to look at the images. The first call for an image makes its missing JPEG preview and keeps it in team storage, so later calls reuse it. |
195
- | `qawolf run optOutOfInvestigation` | write | Mark failed flows in a run as "do not investigate" (DNI): the failures need no bug or maintenance report. Each flow must have failed in the run and still be under investigation. A flow that already has a diagnosis cannot be opted out. A team or organization key records the opt-out as the workspace's automation user. To link a failure to a report instead, use run.diagnose. |
196
- | `qawolf run reattempt` | write | Request new attempts for a run's flows. A flow is eligible once its result is failed or canceled and QA Wolf's automatic retries have finished. A flow that kept failing in later runs is attempted in the latest of them, because that is the run carrying the failure, so read reattemptedInRunIds for where each attempt landed. A fully investigated run no longer accepts reattempts. Attempts run with the latest flow code. Poll run.get for results. |
195
+ | `qawolf run optOutOfInvestigation` | write | Mark failed flows in a run as "do not investigate" (DNI): the failures need no bug report or blocker. Each flow must have failed in the run and still be under investigation. A flow that already has a diagnosis cannot be opted out. A team or organization key records the opt-out as the workspace's automation user. To link a failure to a report instead, use run.diagnose. |
196
+ | `qawolf run reattempt` | write | Request new attempts for a run's flows. A flow is eligible once its result is failed or canceled and QA Wolf's automatic retries have finished. A flow that kept failing in later runs is attempted in the latest of them, because that is the run carrying the failure, so read reattemptedInRunIds for where each attempt landed. A fully investigated run no longer accepts reattempts. Attempts run with the flow code the environment has synced when the request arrives: after publishing a fix, pass afterCommit so the request waits for that commit instead of rerunning older code. Poll run.get for results, or pass aiTaskId or chatSessionId to be notified when they settle. |
197
197
  | `qawolf run restoreScreenshotBaseline` | write | Undo a screenshot baseline change that accepted a failed comparison of the run: put back the baseline it replaced, so later runs compare with the old baseline again. Use it when a person disputes a baseline the AI accepted. Refuses without changing anything when the baseline changed again since. |
198
198
  | `qawolf run stop` | write | Stop a run, including its queued flows and automatic retries. Stopping is asynchronous and can update run-status messages and commit statuses in connected integrations. Repeated requests are safe, and finished runs keep their results. A run that is still being created returns not found; retry once run.get returns the run. If run.get returns a different runId, use that ID. Poll run.get for results. |
199
199
  | `qawolf runner act` | write | Perform one raw action on a runner's screen. A browser runner takes click, double_click, scroll, move, drag, keypress, navigate and type; a mobile runner takes tap, swipe, fill and type. A browser runner answers mobile actions with action-not-supported-on-browser; a mobile runner answers the other browser actions with action-not-supported-on-mobile. Use - to read a whole action as JSON from stdin |
@@ -312,9 +312,9 @@ of calling `act` and then `screenshot`. One call performs the action and writes
312
312
  the screen the runner answers with: half the calls per step, and no delay to
313
313
  guess at between them.
314
314
 
315
- The full workflow is its own guide: how a runner is billed, why the first call
316
- must be a run, the order the commands go in, the see-and-act loop, `exec`, the
317
- recorder, reading history, staying alive, and an end-to-end example. **Run
315
+ The full workflow is its own guide: how a runner is billed, the order the
316
+ commands go in, the see-and-act loop, `exec`, the recorder, reading history,
317
+ staying alive, and an end-to-end example. **Run
318
318
  `qawolf help ref runner` before driving a runner for the first time.** It prints
319
319
  that guide and the help of every runner command, for the CLI version you have.
320
320
  Each command's `--help` carries its own part, so `qawolf runner exec --help`
@@ -193,7 +193,7 @@ Every documented field of the `run.get` response. `[]` marks an array, so
193
193
  - `supersededBy.url` — Absolute URL of the replacement run's page.
194
194
  - `blockingBugCount` — How many bugs this run found are blocking: still open, and priority urgent, high, or unprioritized — unprioritized counts because nobody has ruled it out yet. This is what `failed` is derived from, so it explains a failure rather than adding a second verdict: gate on `status`, then read this to say how many bugs are holding the build. It counts a bug filed against a later run by an investigation that carried over from this one, and it drops a bug once that bug is resolved.
195
195
  - `flows` — The run's flows, ordered alphabetically by name. Only the flows matching flowStatuses when the request set it.
196
- - `flows[].attempts` — The flow's finished execution attempts, oldest first, including manual Wolf Browser attempts. Present once at least one attempt has finished, so a flow that passed after retries also lists its failed attempts. Artifact URLs appear only on automated attempts that reached a verdict, stay valid for at least a day (call run.get again for fresh ones), and can return 404 when the attempt did not produce that artifact.
196
+ - `flows[].attempts` — The flow's finished execution attempts, oldest first, including manual Wolf Browser attempts. Present once at least one attempt has finished, so a flow that passed after retries also lists its failed attempts. Artifact URLs appear only on attempts that reached a verdict, and on a manual attempt only when its Wolf Browser run kept them. They stay valid for at least a day (call run.get again for fresh ones), and can return 404 when the attempt did not produce that artifact.
197
197
  - `flows[].attempts[].logsUrl` — Signed URL for the attempt's execution logs.
198
198
  - `flows[].attempts[].traceUrl` — Signed URL for the attempt's Playwright trace (a trace.zip; open it with `npx playwright show-trace`).
199
199
  - `flows[].attempts[].videoUrl` — Signed URL for the attempt's screen recording.
@@ -201,6 +201,7 @@ Every documented field of the `run.get` response. `[]` marks an array, so
201
201
  - `flows[].attempts[].kind` — One of: automated, manual
202
202
  - `flows[].attempts[].startedAt` — Absent when the attempt failed before it could start.
203
203
  - `flows[].attempts[].status` — One of: passed, failed, canceled
204
+ - `flows[].attempts[].url` — Absolute URL of the attempt's page in the app, which opens this flow at this attempt. Link this page to show one flow's attempt: the run page opens a different flow. Absent only in replies from servers older than this field.
204
205
  - `flows[].attempts[].canceledReason` — Why the attempt was canceled. userCanceled means a person stopped it; do not immediately retry that activity.
205
206
  - `flows[].failure.diagnosis` — QA Wolf's investigation verdict for the failure: `bug` means the application is broken, `maintenance` means the test needed an update and the failure does not indicate an application problem. Absent until the investigation reaches a verdict, and absent when the flow was opted out of investigation. Pass issueId to issue.get for details.
206
207
  - `flows[].failure.diagnosis.issueId` — The id of the issue.
@@ -11,28 +11,23 @@ Commands that target a runner find one in this order: `--runner`, then `QAWOLF_R
11
11
  - `qawolf runner launch` is not in that order: it takes its id from `--id` and never reads `QAWOLF_RUNNER_ID`. Pass `--id` whenever you have an id in mind.
12
12
  - A runner id that is set is treated as found, whether or not anything is running under it. Exporting `QAWOLF_RUNNER_ID=agent-1` turns off the auto-launch described next: instead of starting `agent-1`, commands try to reach it and fail with exit code `8`, naming the id and saying the variable is what chose it. Launch that id once yourself and the rest follows.
13
13
 
14
- If nothing names a runner, the commands that change something launch one and say so on stderr, naming it: `run`, `act` and `exec`. Read that announcement. The browser it just started is fresh: nothing has been run on it, nothing is signed in, and no page is open. Acting as though your earlier setup survived is the single most likely way to drive the wrong page.
14
+ If nothing names a runner, the commands that change something launch one and say so on stderr, naming it: `run`, `act`, `actions` and `exec`. Read that announcement. The browser it just started is fresh: nothing has been run on it, nothing is signed in, and it shows only the QA Wolf welcome page. Acting as though your earlier setup survived is the single most likely way to drive the wrong page.
15
15
 
16
16
  No read command ever launches a runner. `screenshot`, `events` and `keepalive` tell you there is no runner rather than quietly billing one, and so does `terminate`.
17
17
 
18
18
  ## The order that matters
19
19
 
20
- A freshly launched runner has no screen. The virtual desktop starts with the runner's first run and nothing else starts it, so until you have run something:
20
+ A playwright runner's screen starts as it launches, showing a QA Wolf welcome page, so the screenshot-and-act loop works before you run anything.
21
21
 
22
- - `screenshot` and `act` fail with exit code `2`, except `navigate`, which fails with exit code `1` (`action-failed`): it skips the screen but still needs the runner to have run something
23
- - `exec` fails with exit code `2`
24
- - `events recorder` reads as empty
25
-
26
- None of that is a fault, and none of it clears on its own. Only `qawolf runner run <flow>` starts the screen. A bare navigate does not: it fails until the first run, however long you wait.
27
-
28
- So the first thing you do to a new runner has to put a browser on it. That means a flow file and a `package.json` on disk, even if all you want is to drive the browser by hand; there is no "just give me a screen" call. Once one run has happened, the screenshot-and-act loop works for the rest of the runner's life. A `--lines` selection is the one call that does not need a run first.
22
+ Any other runner, such as a mobile one, has no screen until its first run, and nothing else starts it. Until you have run something on it, `screenshot` and `act` fail with exit code `2`. That is not a fault, and it does not clear on its own: run a flow with `qawolf runner run <flow>`, which needs a flow file and a `package.json` on disk.
29
23
 
30
24
  ## Exit codes
31
25
 
32
26
  Retry on the exit code, not on the message text:
33
27
 
34
- - `4` is transient, with one exception. The screen is up but cannot serve this instant: restarting after a display-size change, or busy with another request. Retry in a second or two, and bound the retries. The exception is a command that changes something, where a `4` can instead mean the answer was lost with the work in flight. For `act` and `actions`, take a screenshot first and repeat only what the screen says did not happen. For `run`, poll `run-status` instead of submitting again, since a second submission risks a second billed run. For `exec`, check the effect the snippet was meant to have before running it again.
28
+ - `4` is transient, with one exception. The screen cannot serve this instant: still coming up just after launch, restarting after a display-size change, or busy with another request. Retry in a second or two, and bound the retries. The exception is a command that changes something, where a `4` can instead mean the answer was lost with the work in flight. For `act` and `actions`, take a screenshot first and repeat only what the screen says did not happen. For `run`, poll `run-status` instead of submitting again, since a second submission risks a second billed run. For `exec`, check the effect the snippet was meant to have before running it again.
35
29
  - `6` means the work ran out of the time it is given.
30
+ - `7` means billing prevented the request, such as a plan that does not cover the runner you asked for. The message says what was refused and what clears it.
36
31
  - `8` means there is no such runner. It was never launched, or it was terminated, or it idled out. Retrying never brings one back, so stop and launch the id or name one that is running. The message says which runner was meant and whether `--runner`, `QAWOLF_RUNNER_ID` or this directory's stored default chose it; read that line before you pick an id to launch.
37
32
  - `2` will not clear on its own. Nothing has run on this runner yet, so run a flow; or the runner has no browser at all, so launch with `--name playwright` instead; or the action belongs to the other runner family, so send `tap`, `swipe` or `fill` to a mobile runner and the browser actions to a browser runner. The message says which.
38
33
 
@@ -40,14 +35,14 @@ Retry on the exit code, not on the message text:
40
35
 
41
36
  ## End to end
42
37
 
43
- Run from a directory holding a flow and a `package.json`. The run is what starts the screen, so it is not optional even though the goal here is to drive by hand.
38
+ Run from a directory holding a flow and a `package.json`.
44
39
 
45
40
  ```sh
46
41
  export QAWOLF_API_KEY=... # the only credential
47
42
  export QAWOLF_RUNNER_ID=agent-1 # so no command below needs --runner
48
43
 
49
44
  qawolf runner launch --id agent-1 --json # --id, not the variable; read .alreadyRunning and .url
50
- qawolf runner run flows/smoke.flow.ts --follow # starts the screen; exit 1 if it failed
45
+ qawolf runner run flows/smoke.flow.ts --follow # exit 1 if it failed
51
46
 
52
47
  qawolf runner act navigate --url https://example.com/login --screenshot step-1.jpg # then read step-1.jpg yourself
53
48
  qawolf runner act click --button left --x 480 --y 260 --screenshot step-2.jpg
@@ -144,8 +139,8 @@ Ids:
144
139
  fine id. Launching an id that is already running attaches to that runner
145
140
  instead of starting and billing a second one, and the answer says which
146
141
  happened: read `alreadyRunning`. Reusing one id is therefore the cheap and
147
- safe pattern. The same id with a different --name is refused rather than
148
- silently ignored.
142
+ safe pattern. --name does not change a runner that is already running: the
143
+ answer's `runnerName` says what you attached to.
149
144
 
150
145
  launch takes its id from --id and never reads QAWOLF_RUNNER_ID. A bare `qawolf
151
146
  runner launch` invents a random id, bills a pod under it and stores it, so a
@@ -164,9 +159,10 @@ The page:
164
159
  launched its own runner. It is a QA Wolf page showing what the runner is
165
160
  doing, where a person can also take over with their own mouse and keyboard.
166
161
  Hand it to a person who asks what your runner is up to. The page opens for
167
- anyone on the runner's team, however the runner was launched. There is nothing
168
- to see until the runner's first run starts its screen, so the page waits until
169
- then. You read the screen with `screenshot`, not with the page.
162
+ anyone on the runner's team, however the runner was launched. A playwright
163
+ runner's screen starts as it launches, showing a QA Wolf welcome page. Any
164
+ other runner's screen starts with its first run, so its page waits until then.
165
+ You read the screen with `screenshot`, not with the page.
170
166
 
171
167
  Browser or mobile:
172
168
  --name also chooses between a browser and a mobile device: --name android or
@@ -186,7 +182,7 @@ Usage: qawolf runner list [options]
186
182
  List the runners running on your team
187
183
 
188
184
  Options:
189
- --here Only the runners this directory launched
185
+ --here Only the runners this directory launched or QAWOLF_RUNNER_ID names
190
186
  -h, --help display help for command
191
187
 
192
188
  Examples:
@@ -195,12 +191,11 @@ Examples:
195
191
  $ qawolf runner list --json
196
192
 
197
193
  What the list holds:
198
- The list names the runners this directory has launched that are still running,
199
- and marks the one a command with no --runner would reach. It also includes the
200
- runner named by QAWOLF_RUNNER_ID even though this directory did not launch it,
201
- so a harness handed a runner sees it alongside the ones it started itself. Use
202
- the id column with --runner to address any of them; addressing one does not
203
- make it the default.
194
+ The list names every active runner on your team, marking the ones this
195
+ directory launched and the default, the one a command with no --runner would
196
+ reach. --here keeps only this directory's runners and the one QAWOLF_RUNNER_ID
197
+ names. Use the id column with --runner to address any of them; addressing one
198
+ does not make it the default.
204
199
 
205
200
  Every runner is looked up before it is listed, so a runner that idled out is
206
201
  absent rather than reported. The lookup neither starts a runner nor resets an
@@ -514,10 +509,11 @@ The recorder:
514
509
  `code` is absent on events with no call of their own, such as a navigation,
515
510
  which is why the first line falls back to `type`. Use these to turn a session
516
511
  you drove by pixel coordinates into durable selectors, and to check that a
517
- click landed on the element you meant rather than near it. The stream is empty
518
- until the runner's first run gives it a browser context, so an early empty
519
- answer means "not yet", not "broken". Do not add --json here: it wraps each
520
- line in an envelope and these field paths stop matching.
512
+ click landed on the element you meant rather than near it. The stream stays
513
+ empty while a playwright runner still shows its welcome page, and on any other
514
+ runner until its first run, so an early empty answer means "not yet", not
515
+ "broken". Do not add --json here: it wraps each line in an envelope and these
516
+ field paths stop matching.
521
517
 
522
518
  Following:
523
519
  --follow polls and prints as entries arrive. It is tail -f with a bound: it
@@ -566,9 +562,10 @@ Reading the screen:
566
562
  to stderr so nothing follows the image on stdout. A terminal on stdout is
567
563
  refused: redirect or pipe it.
568
564
 
569
- A runner has no screen until its first run, so until then screenshot exits 2.
570
- It never launches a runner. When you are about to act anyway, `act
571
- --screenshot` performs the action and returns the screen in one call.
565
+ A playwright runner's screen starts as it launches. Any other runner has no
566
+ screen until its first run, so until then screenshot exits 2 on it. It never
567
+ launches a runner. When you are about to act anyway, `act --screenshot`
568
+ performs the action and returns the screen in one call.
572
569
  ```
573
570
 
574
571
  ## qawolf runner act
@@ -583,7 +580,7 @@ other browser actions with action-not-supported-on-mobile. Use - to read a whole
583
580
  stdin
584
581
 
585
582
  Options:
586
- --button <button> click: left, right, wheel, back or forward
583
+ --button <button> click: left (default), right, wheel, back or forward
587
584
  --duration-ms <ms> swipe: how long it takes, up to 10000. Slow scrolls, fast flings
588
585
  --from <x,y> swipe: the point it starts at
589
586
  --keys <keys...> keypress: modifiers and the key, e.g. Control a
@@ -670,10 +667,10 @@ Mobile:
670
667
  swipe and fill with action-not-supported-on-browser.
671
668
 
672
669
  Before the first run:
673
- A runner has no screen until its first run, so act exits 2 until then, except
674
- navigate, which exits 1 (action-failed): it skips the screen but still needs
675
- the runner to have run something. With no runner named at all, act launches
676
- one and says so on stderr.
670
+ A playwright runner's screen starts as it launches, so act works on it before
671
+ anything has run. Any other runner has no screen until its first run, so act
672
+ exits 2 on it until then. With no runner named at all, act launches one and
673
+ says so on stderr.
677
674
  ```
678
675
 
679
676
  ## qawolf runner actions
@@ -798,12 +795,12 @@ Scope:
798
795
  files, so the snippet can use your own page objects and helpers.
799
796
 
800
797
  Failures:
801
- exec exits 2 until the runner's first run, since there is no page to evaluate
802
- against. On a 4 the message says the snippet could not be evaluated, but a
803
- lost answer looks the same from outside, so treat a 4 from a snippet that
804
- changes something as "may have run" rather than "did not run", and check its
805
- effect before running it again. With no runner named at all, exec launches one
806
- and says so on stderr.
798
+ A playwright runner has a page to evaluate against as soon as it launches. On
799
+ a 4 the message says the snippet could not be evaluated, but a lost answer
800
+ looks the same from outside, so treat a 4 from a snippet that changes
801
+ something as "may have run" rather than "did not run", and check its effect
802
+ before running it again. With no runner named at all, exec launches one and
803
+ says so on stderr.
807
804
  ```
808
805
 
809
806
  ## qawolf runner inspect