test: fake colab CLI + PTY harness + opt-in live smoke #5
Labels
No labels
area/backup
area/cli
area/docs
area/dsh
area/forgejo
area/host
area/mcp
area/plugin
area/security
area/ux
needs-operator
priority/later
priority/next
priority/now
type/bug
type/research
type/task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dsh-plugins/dsh-colab#5
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Unit tests without a VM + one cheap live smoke test.
Unit (no network/GPU)
colabexecutable on PATH (shell or node script) with canned outputs for: new/status/stop/usage/log/drivemount/ls/upload/downloadsession_not_found, rate limit, auth pending, wedged kernelIntegration (opt-in, ~1 CU)
execprint torch version → stop; assert cleanup even on failureAcceptance
npm test(or equivalent) green offline;make smoke/ env-gated;Mostly done in
f414adc; keeping open until the live smoke runs.test/fake-colab.mjsreproduces the 0.8.0 text formats and a small remote filesystem (sessions, usage, log JSONL, ls, upload/download, exec with ticks/appends/writes/timeout/exit, Drive auth with consent-file control, upload 500s, hanging commands)test/helpers/harness.mjsgives each test an isolated fake CLI + fake Cordis context and validates every tool result against its output schemanpm test, including a fullcolab_runrecipe with artifact verification, stop-on-every-path, redaction, and MCP adapter tests with a fake MCP clientscripts/smoke-live.mjsshipped, guarded byDSH_COLAB_LIVE_SMOKE=1+--confirm-live; it creates only its ownsmoke-<hex>session, optionally tests Drive, and always stops itNot run: the live smoke. This host has no
colabbinary on purpose and the operator may have sessions running; the first real run should be a deliberate, operator-present action.