@@ -318,17 +318,17 @@ Matrix has a [dedicated page](/concepts/qa-matrix) because of its scenario count
318318319319These lanes register through `extensions/qa-lab/src/live-transports/shared/live-transport-cli.ts` and accept the same flags:
320320321-| Flag | Default | Description |
322-| ------------------------------------- | -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
323-| `--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). |
328-| `--model <ref>` / `--alt-model <ref>` | provider default | Primary/alternate model refs. |
329-| `--fast` | off | Provider fast mode where supported. |
330-| `--credential-source <env\|convex>` | `env` | See [Convex credential pool](#convex-credential-pool). |
331-| `--credential-role <maintainer\|ci>` | `ci` in CI, `maintainer` otherwise | Role used when `--credential-source convex`. |
321+| Flag | Default | Description |
322+| ------------------------------------- | -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
323+| `--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). |
328+| `--model <ref>` / `--alt-model <ref>` | provider default | Primary/alternate model refs. |
329+| `--fast` | off | Provider fast mode where supported. |
330+| `--credential-source <env\|convex>` | `env` | See [Convex credential pool](#convex-credential-pool). |
331+| `--credential-role <maintainer\|ci>` | `ci` in CI, `maintainer` otherwise | Role used when `--credential-source convex`. |
332332333333Each lane exits non-zero on any failed scenario. `--allow-failures` writes artifacts without setting a failing exit code.
334334@@ -346,10 +346,6 @@ Required env when `--credential-source env`:
346346- `OPENCLAW_QA_TELEGRAM_DRIVER_BOT_TOKEN`
347347- `OPENCLAW_QA_TELEGRAM_SUT_BOT_TOKEN`
348348349-Optional:
350-351-- `OPENCLAW_QA_TELEGRAM_CAPTURE_CONTENT=1` keeps message bodies in observed-message artifacts (default redacts).
352-353349Scenarios (`extensions/qa-lab/src/live-transports/telegram/telegram-live.runtime.ts`):
354350355351- `telegram-canary`
@@ -375,26 +371,26 @@ Output artifacts:
375371376372- `telegram-qa-report.md`
377373- `qa-evidence.json` - evidence entries for the live transport checks, including profile, coverage, provider, channel, artifacts, result, and RTT fields.
378-- `telegram-qa-observed-messages.json` - bodies redacted unless `OPENCLAW_QA_TELEGRAM_CAPTURE_CONTENT=1`.
379374380-Package RTT comparison uses the same Telegram credential contract while keeping
381-its RTT sample controls on the RTT harness path:
375+Package Telegram runs use the same Telegram credential contract. Repeated RTT
376+measurement is part of the normal package Telegram live lane; the RTT
377+distribution is folded into `qa-evidence.json` under `result.timing` for the
378+selected RTT check.
382379383380```bash
384-pnpm rtt openclaw@beta \
385- --credential-source convex \
386- --credential-role maintainer \
387- --samples 20 \
388- --sample-timeout-ms 30000
381+OPENCLAW_QA_CREDENTIAL_SOURCE=convex \
382+pnpm test:docker:npm-telegram-live
389383```
390384391-When `--credential-source convex` is set, the RTT Docker wrapper leases a
392-`kind: "telegram"` credential, exports the leased group/driver/SUT bot env into
393-the installed-package run, heartbeats the lease, and releases it on shutdown.
394-`--samples` and `--sample-timeout-ms` still feed
395-`OPENCLAW_NPM_TELEGRAM_WARM_SAMPLES` and
396-`OPENCLAW_NPM_TELEGRAM_SAMPLE_TIMEOUT_MS`, so `result.json` remains comparable
397-across env-backed and Convex-backed RTT runs.
385+When `OPENCLAW_QA_CREDENTIAL_SOURCE=convex` is set, the package live wrapper
386+leases a `kind: "telegram"` credential, exports the leased group/driver/SUT bot
387+env into the installed-package run, heartbeats the lease, and releases it on
388+shutdown. The package wrapper defaults to 20 RTT checks of
389+`telegram-mentioned-message-reply`, a 30s RTT timeout, and Convex role
390+`maintainer` outside CI when Convex is selected. Override
391+`OPENCLAW_NPM_TELEGRAM_RTT_SAMPLES`, `OPENCLAW_NPM_TELEGRAM_RTT_TIMEOUT_MS`,
392+or `OPENCLAW_NPM_TELEGRAM_RTT_MAX_FAILURES` to tune RTT measurement without
393+creating a separate RTT command or Telegram-specific summary format.
398394399395### Discord QA
400396此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。