History

Hongming Wang f4700858ac feat(e2e): canary + canvas Playwright workflows; delegation mechanics Three additions on top of `187a9bf`: 1. Canary (.github/workflows/canary-staging.yml) 30-min cron that runs the full-SaaS harness in E2E_MODE=canary: one hermes workspace + one A2A PONG + teardown. ~8-min wall clock vs ~20-min for the full run. Alerting is self-contained: opens a single 'Canary failing' issue on first failure, comments on subsequent failures (no issue spam), auto-closes the issue on the next green run. Labels: canary-staging, bug. Safety-net teardown step sweeps e2e-YYYYMMDD-canary-* orgs tagged today so a runner cancel can't leak EC2. 2. Canvas Playwright (canvas/e2e/staging-*.ts + playwright.staging.config.ts + .github/workflows/e2e-staging-canvas.yml) staging-setup.ts provisions a fresh org + hermes workspace (same lifecycle as the bash harness, just in TypeScript). staging-tabs.spec.ts clicks through all 13 workspace-panel tabs (chat, activity, details, skills, terminal, config, schedule, channels, files, memory, traces, events, audit) and asserts each renders without crashing and without 'Failed to load' error toasts. Known SaaS gaps (Files empty, Terminal disconnects, Peers 401) are documented in #1369 and whitelisted so they don't fail the test — the gate is 'no hard crash', not 'no issues'. staging-teardown.ts deletes the org via DELETE /cp/admin/tenants/:slug. playwright.staging.config.ts separates staging from local tests so pnpm test in dev doesn't try to provision against staging. Retries=2 and timeouts are longer; workers=1 because the setup provisions one shared workspace. Workflow uploads HTML report + screenshots on failure for 14 days. 3. Delegation mechanics (tests/e2e/test_staging_full_saas.sh section 10) Parent → child proxy test: POST /workspaces/CHILD/a2a with X-Source-Workspace-Id=PARENT and verify the child responds + child activity log captures PARENT as source. Intentionally LLM-free: the mechanics regression is what matters; prompt-driven delegation correctness belongs in canvas-driven tests. Also reorders teardown step to 11/11 since delegation is 10/11. Mode gating: E2E_MODE=canary -> skips child workspace, HMA memory, peers, activity, delegation (steps 6, 9, 10 no-op). Full-lifecycle still runs every piece. Validated both paths via 'bash -n' syntax check after each edit. Secrets requirement unchanged (same two secrets as `187a9bf`): MOLECULE_STAGING_SESSION_COOKIE, MOLECULE_STAGING_ADMIN_TOKEN. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-04-21 04:15:10 -07:00
..
e2e	feat(e2e): canary + canvas Playwright workflows; delegation mechanics	2026-04-21 04:15:10 -07:00
README.md	chore: final open-source cleanup — binary, stale paths, private refs	2026-04-18 00:38:55 -07:00

Hongming Wang f4700858ac feat(e2e): canary + canvas Playwright workflows; delegation mechanics

Three additions on top of 187a9bf:

1. Canary (.github/workflows/canary-staging.yml)
   30-min cron that runs the full-SaaS harness in E2E_MODE=canary: one
   hermes workspace + one A2A PONG + teardown. ~8-min wall clock vs
   ~20-min for the full run.
   Alerting is self-contained: opens a single 'Canary failing' issue on
   first failure, comments on subsequent failures (no issue spam),
   auto-closes the issue on the next green run. Labels: canary-staging,
   bug. Safety-net teardown step sweeps e2e-YYYYMMDD-canary-* orgs
   tagged today so a runner cancel can't leak EC2.

2. Canvas Playwright (canvas/e2e/staging-*.ts + playwright.staging.config.ts
   + .github/workflows/e2e-staging-canvas.yml)
   staging-setup.ts provisions a fresh org + hermes workspace (same
   lifecycle as the bash harness, just in TypeScript). staging-tabs.spec.ts
   clicks through all 13 workspace-panel tabs (chat, activity, details,
   skills, terminal, config, schedule, channels, files, memory, traces,
   events, audit) and asserts each renders without crashing and without
   'Failed to load' error toasts. Known SaaS gaps (Files empty, Terminal
   disconnects, Peers 401) are documented in #1369 and whitelisted so
   they don't fail the test — the gate is 'no hard crash', not 'no
   issues'.
   staging-teardown.ts deletes the org via DELETE /cp/admin/tenants/:slug.
   playwright.staging.config.ts separates staging from local tests so
   pnpm test in dev doesn't try to provision against staging. Retries=2
   and timeouts are longer; workers=1 because the setup provisions one
   shared workspace. Workflow uploads HTML report + screenshots on
   failure for 14 days.

3. Delegation mechanics (tests/e2e/test_staging_full_saas.sh section 10)
   Parent → child proxy test: POST /workspaces/CHILD/a2a with
   X-Source-Workspace-Id=PARENT and verify the child responds + child
   activity log captures PARENT as source. Intentionally LLM-free: the
   mechanics regression is what matters; prompt-driven delegation
   correctness belongs in canvas-driven tests.
   Also reorders teardown step to 11/11 since delegation is 10/11.

Mode gating:
   E2E_MODE=canary -> skips child workspace, HMA memory, peers,
   activity, delegation (steps 6, 9, 10 no-op). Full-lifecycle still
   runs every piece. Validated both paths via 'bash -n' syntax check
   after each edit.

Secrets requirement unchanged (same two secrets as 187a9bf):
  MOLECULE_STAGING_SESSION_COOKIE, MOLECULE_STAGING_ADMIN_TOKEN.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-21 04:15:10 -07:00

e2e feat(e2e): canary + canvas Playwright workflows; delegation mechanics 2026-04-21 04:15:10 -07:00

README.md chore: final open-source cleanup — binary, stale paths, private refs 2026-04-18 00:38:55 -07:00

README.md

Tests

This repo uses the standard monorepo testing convention: unit tests live with their package, cross-component E2E tests live here.

Where to find tests

Scope	Location
Go unit + integration (platform, CLI, handlers)	`workspace-server/*/_test.go` — run with `cd workspace-server && go test -race ./...`
TypeScript unit (canvas components, hooks, store)	`canvas/src/**/__tests__/` — run with `cd canvas && npm test -- --run`
TypeScript unit (MCP server handlers)	`mcp-server/src/__tests__/` — run with `cd mcp-server && npx jest`
Python unit (workspace runtime, adapters)	`workspace/tests/` — run with `cd workspace && python3 -m pytest`
Python unit (SDK: plugin + remote agent)	`sdk/python/tests/` — run with `cd sdk/python && python3 -m pytest`
Cross-component E2E (spans platform + runtime + HTTP)	`tests/e2e/` ← you are here

Why split this way

Go requires co-located _test.go files to access unexported symbols.
Per-package test commands keep the inner loop fast — changing canvas doesn't re-run Go tests.
tests/e2e/ covers scenarios that no single package owns: a full workspace lifecycle, A2A across two provisioned agents, delegation chains, bundle round-trips.

Running E2E

Every E2E script here assumes the platform is running at localhost:8080 and (where noted) provisioned agents are online. See the header comment of each .sh for specifics.

Cleaning up rogue test workspaces

If an E2E run aborts before its teardown runs (Ctrl-C, crash, CI timeout), the platform can be left with workspaces whose config volume is stale or empty — Docker's unless-stopped restart policy then spins those containers in a FileNotFoundError loop. The platform's pre-flight check (#17) marks such workspaces failed on the next restart, but a manual cleanup is useful:

bash scripts/cleanup-rogue-workspaces.sh               # deletes ws with id/name starting aaaaaaaa-, bbbbbbbb-, cccccccc-, test-ws-
MOLECULE_URL=http://host:8080 bash scripts/cleanup-rogue-workspaces.sh

The script DELETEs each matching workspace via the API and force-removes the ws-<id[:12]> container as a belt-and-suspenders fallback.