docs(qa): document telegram e2e defaults · openclaw/openc...
obviyus
·
2026-05-08
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -278,7 +278,7 @@ Optional:
|
278 | 278 | |
279 | 279 | - `OPENCLAW_QA_TELEGRAM_CAPTURE_CONTENT=1` keeps message bodies in observed-message artifacts (default redacts). |
280 | 280 | |
281 | | -Scenarios (`extensions/qa-lab/src/live-transports/telegram/telegram-live.runtime.ts:44`): |
| 281 | +Scenarios (`extensions/qa-lab/src/live-transports/telegram/telegram-live.runtime.ts`): |
282 | 282 | |
283 | 283 | - `telegram-canary` |
284 | 284 | - `telegram-mention-gating` |
@@ -287,10 +287,17 @@ Scenarios (`extensions/qa-lab/src/live-transports/telegram/telegram-live.runtime
|
287 | 287 | - `telegram-commands-command` |
288 | 288 | - `telegram-tools-compact-command` |
289 | 289 | - `telegram-whoami-command` |
| 290 | +- `telegram-status-command` |
| 291 | +- `telegram-other-bot-command-gating` |
290 | 292 | - `telegram-context-command` |
| 293 | +- `telegram-current-session-status-tool` |
| 294 | +- `telegram-reply-chain-exact-marker` |
| 295 | +- `telegram-stream-final-single-message` |
291 | 296 | - `telegram-long-final-reuses-preview` |
292 | 297 | - `telegram-long-final-three-chunks` |
293 | 298 | |
| 299 | +The implicit default set always covers canary, mention gating, native command replies, command addressing, and bot-to-bot group replies. `mock-openai` defaults also include deterministic reply-chain and final-message streaming checks. `telegram-current-session-status-tool` remains opt-in because it is only stable when threaded directly after canary, not after arbitrary native command replies. Use `pnpm openclaw qa telegram --list-scenarios --provider-mode mock-openai` to print the current default/optional split with regression refs. |
| 300 | + |
294 | 301 | Output artifacts: |
295 | 302 | |
296 | 303 | - `telegram-qa-report.md` |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -311,6 +311,7 @@ gh workflow run package-acceptance.yml --ref main \
|
311 | 311 | - Runs the Telegram live QA lane against a real private group using the driver and SUT bot tokens from env. |
312 | 312 | - Requires `OPENCLAW_QA_TELEGRAM_GROUP_ID`, `OPENCLAW_QA_TELEGRAM_DRIVER_BOT_TOKEN`, and `OPENCLAW_QA_TELEGRAM_SUT_BOT_TOKEN`. The group id must be the numeric Telegram chat id. |
313 | 313 | - Supports `--credential-source convex` for shared pooled credentials. Use env mode by default, or set `OPENCLAW_QA_CREDENTIAL_SOURCE=convex` to opt into pooled leases. |
| 314 | + - Defaults cover canary, mention gating, command addressing, `/status`, bot-to-bot mentioned replies, and core native command replies. `mock-openai` defaults also cover deterministic reply-chain and Telegram final-message streaming regressions. Use `--list-scenarios` for optional probes such as `session_status`. |
314 | 315 | - Exits non-zero when any scenario fails. Use `--allow-failures` when you |
315 | 316 | want artifacts without a failing exit code. |
316 | 317 | - Requires two distinct bots in the same private group, with the SUT bot exposing a Telegram username. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
