fanhuadesenlinnn/tdesktop
1
0
Fork 0
mirror of https://hubproxy.babadafafafafa.cn/https://github.com/telegramdesktop/tdesktop synced 2026-09-20 08:03:45 +08:00
Code Issues Packages Projects Releases Wiki Activity

[ai] Allow modifying test account data.

Browse Source
This commit is contained in:
John Preston
2026-07-17 17:44:07 +04:00
parent f1ce6ee699
commit 3dc6ca3951
2 changed files with 14 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
.agents/shared/test-loop.md
View File

@@ -136,10 +136,16 @@ account, and MUST be left alive. On Windows, scope the kill by path:
and takes down the user's unrelated clients. Every "kill stragglers" / "taskkill" step below means
this path-scoped kill.
**Avoid destructive calls.** The overlay must never trigger logout / session-termination /
account-deletion. Tests that genuinely need those use a separate burner account, not this one. (If a
permanent destructive-call fuse is later added to the debug build, this is enforced in code; until
then it is the test-author's responsibility.)
**Avoid account-fatal calls; cloud data is otherwise fair game.** The overlay must never trigger
logout / session-termination / account-deletion, and must not wipe the account wholesale. Tests that
genuinely need those use a separate burner account, not this one. (If a permanent destructive-call
fuse is later added to the debug build, this is enforced in code; until then it is the
test-author's responsibility.) Everything short of that is allowed: this is a test-server account,
so freely CREATE content in any chats (messages, drafts, tables, media) and freely DELETE or clear
content that test runs created — including leftovers from previous runs and sessions (e.g. clear
the self-chat rich compose cloud draft before a run instead of designing around accumulated junk;
cloud drafts survive the local tdata restore, so server-side cleanup is the right tool). Don't
delete anything the user placed on the account by hand unless the task says so.
## Design the tests from THIS task (the crux)

5
.claude/commands/implement.md
View File

@@ -329,7 +329,10 @@ stays in YOUR context, not the orchestrator's):
new IMPL_SHA). After each run, save the overlay patch into TASK_DIR and `git reset --hard
<IMPL_SHA>` so the checkout returns to impl-only. Run the test-account SETUP steps before each
launch, set the run-specific `EVIDENCE_DIR`, and honor every test-account hard rule (serialize
app runs; avoid destructive calls).
app runs; avoid account-fatal calls — logout/session-termination/account-deletion/whole-account
wipe. Other cloud-side changes are fine: it is a test-server account, so create content in any
chats freely and delete/clear content that test runs created, even in earlier runs — e.g. clear
a junk-accumulated cloud draft before a run instead of designing the oracle around it).
Skip TEST only if the task changed no runnable behavior (docs/config only) — say so explicitly.