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
|`--scenario <id>`| - | Run only this scenario. Repeatable. |
324
-
|`--output-dir <path>`|`<repo>/.artifacts/qa-e2e/<transport>-<timestamp>`| Where reports/summary/observed messages and the output log are written. Relative paths resolve against `--repo-root`. |
325
-
|`--repo-root <path>`|`process.cwd()`| Repository root when invoking from a neutral cwd. |
326
-
|`--sut-account <id>`|`sut`| Temporary account id inside the QA gateway config. |
327
-
|`--provider-mode <mode>`|`live-frontier`|`mock-openai` or `live-frontier` (legacy `live-openai` still works). |
|`--scenario <id>`| - | Run only this scenario. Repeatable. |
324
+
|`--output-dir <path>`|`<repo>/.artifacts/qa-e2e/<transport>-<timestamp>`| Where reports, summaries, evidence, transport-specific artifacts, and the output log are written. Relative paths resolve against `--repo-root`. |
325
+
|`--repo-root <path>`|`process.cwd()`| Repository root when invoking from a neutral cwd. |
326
+
|`--sut-account <id>`|`sut`| Temporary account id inside the QA gateway config. |
327
+
|`--provider-mode <mode>`|`live-frontier`|`mock-openai` or `live-frontier` (legacy `live-openai` still works). |
-`qa-evidence.json` - evidence entries for the live transport checks, including profile, coverage, provider, channel, artifacts, result, and RTT fields.
Copy file name to clipboardExpand all lines: docs/help/testing.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -218,17 +218,27 @@ inside every shard.
218
218
`OPENCLAW_NPM_TELEGRAM_PACKAGE_TGZ=/path/to/openclaw-current.tgz` or
219
219
`OPENCLAW_CURRENT_PACKAGE_TGZ` to test a resolved local tarball instead of
220
220
installing from the registry.
221
+
- Emits repeated RTT timing in `qa-evidence.json` by default with
222
+
`OPENCLAW_NPM_TELEGRAM_RTT_SAMPLES=20`. Override
223
+
`OPENCLAW_NPM_TELEGRAM_RTT_SAMPLES`,
224
+
`OPENCLAW_NPM_TELEGRAM_RTT_TIMEOUT_MS`, or
225
+
`OPENCLAW_NPM_TELEGRAM_RTT_MAX_FAILURES` to tune the RTT run.
226
+
`OPENCLAW_NPM_TELEGRAM_RTT_CHECKS` accepts a comma-separated list of
227
+
Telegram QA check IDs to sample; when unset, the default RTT-capable check
228
+
is `telegram-mentioned-message-reply`.
221
229
- Uses the same Telegram env credentials or Convex credential source as
222
230
`pnpm openclaw qa telegram`. For CI/release automation, set
223
231
`OPENCLAW_NPM_TELEGRAM_CREDENTIAL_SOURCE=convex` plus
224
-
`OPENCLAW_QA_CONVEX_SITE_URL` and the role secret. If
232
+
`OPENCLAW_QA_CONVEX_SITE_URL` and a role secret. If
225
233
`OPENCLAW_QA_CONVEX_SITE_URL` and a Convex role secret are present in CI,
226
234
the Docker wrapper selects Convex automatically.
227
235
- The wrapper validates Telegram or Convex credential env on the host before
228
236
Docker build/install work. Set `OPENCLAW_NPM_TELEGRAM_SKIP_CREDENTIAL_PREFLIGHT=1`
229
237
only when deliberately debugging pre-credential setup.
230
238
-`OPENCLAW_NPM_TELEGRAM_CREDENTIAL_ROLE=ci|maintainer` overrides the shared
231
-
`OPENCLAW_QA_CREDENTIAL_ROLE` for this lane only.
239
+
`OPENCLAW_QA_CREDENTIAL_ROLE` for this lane only. When Convex credentials
240
+
are selected and no role is set, the wrapper uses `ci` in CI and
241
+
`maintainer` outside CI.
232
242
- GitHub Actions exposes this lane as the manual maintainer workflow
233
243
`NPM Telegram Beta E2E`. It does not run on merge. The workflow uses the
234
244
`qa-live-shared` environment and Convex CI credential leases.
@@ -344,11 +354,11 @@ gh workflow run package-acceptance.yml --ref main \
344
354
want artifacts without a failing exit code.
345
355
- Requires two distinct bots in the same private group, with the SUT bot exposing a Telegram username.
346
356
- For stable bot-to-bot observation, enable Bot-to-Bot Communication Mode in`@BotFather`for both bots and ensure the driver bot can observe group bot traffic.
347
-
- Writes a Telegram QA report, summary, and observed-messages artifact under `.artifacts/qa-e2e/...`. Replying scenarios include RTT from driver send request to observed SUT reply.
357
+
- Writes a Telegram QA report, summary, and `qa-evidence.json` under `.artifacts/qa-e2e/...`. Replying scenarios include RTT from driver send request to observed SUT reply.
348
358
349
359
`Mantis Telegram Live` is the PR-evidence wrapper around this lane. It runs the
350
-
candidate ref with Convex-leased Telegram credentials, renders the redacted
351
-
observed-message transcriptin a Crabbox desktop browser, records MP4 evidence,
360
+
candidate ref with Convex-leased Telegram credentials, renders the redacted QA
361
+
report/evidence bundlein a Crabbox desktop browser, records MP4 evidence,
352
362
generates a motion-trimmed GIF, uploads the artifact bundle, and posts inline PR
353
363
evidence through the Mantis GitHub App when `pr_number` is set. Maintainers can
354
364
start it from the Actions UI through `Mantis Scenario` (`scenario_id:
0 commit comments