History

claude-ceo-assistant 8f1d24f33f fix(ci): canonicalize MOLECULE_STAGING_ADMIN_TOKEN -> CP_STAGING_ADMIN_API_TOKEN (post-#443 rebase) + drop staging-smoke continue-on-error Re-applies PR#462 on current main (PR#443 merged first and renamed canary-staging.yml -> staging-smoke.yml, conflicting #462). Swept 6 files (15 secret-ref flips): - .gitea/workflows/staging-smoke.yml (3 refs + drop continue-on-error + add notify-on-failure step) - .gitea/workflows/e2e-staging-saas.yml (3 refs) - .gitea/workflows/e2e-staging-sanity.yml (3 refs) - .gitea/workflows/e2e-staging-canvas.yml (3 refs) - .gitea/workflows/e2e-staging-external.yml (3 refs) - tests/e2e/STAGING_SAAS_E2E.md (1 heading flip + 1 historical-rename breadcrumb) Each workflow keeps one inline breadcrumb comment pointing back to the old name and internal#322. staging-smoke is the 30-min canary cadence for the entire staging SaaS stack; silent failure (continue-on-error: true) masked exactly the regressions the smoke exists to surface, same class as PR#461 (`sweep-stale-e2e-orgs`). Dropped continue-on-error from the smoke job + added a fail-loud `if: failure()` Notify step mirroring PR#461. The four other `e2e-staging-*` workflows KEEP continue-on-error: true per RFC #219 §1 — they are advisory. Excluded from this PR: - .gitea/workflows/sweep-stale-e2e-orgs.yml (PR#461 owns) - .gitea/workflows/staging-verify.yml (only references the plural MOLECULE_STAGING_ADMIN_TOKENS canary-fleet secret, out of scope) - scripts/staging-smoke.sh (same — plural only) - docs/architecture/canary-release.md (same — plural only) - .github/ mirror tree (separate scope per reference_molecule_core_actions_gitea_only) Verified locally: yaml.safe_load clean on all 5 workflows; grep returns ZERO non-breadcrumb references in the swept files; the plural MOLECULE_STAGING_ADMIN_TOKENS references in staging-verify.yml / scripts/staging-smoke.sh / canary-release.md are intentionally untouched. Refs: internal#322, PR#461, feedback_rename_pr_and_edit_pr_conflict_sequence		2026-05-11 04:33:56 -07:00
..
e2e	fix(ci): canonicalize MOLECULE_STAGING_ADMIN_TOKEN -> CP_STAGING_ADMIN_API_TOKEN (post-#443 rebase) + drop staging-smoke continue-on-error	2026-05-11 04:33:56 -07:00
harness	ci(docker): pin base image digests in all Dockerfiles	2026-05-09 23:56:39 +00:00
ops	ops: add Railway SHA-pin drift audit script + regression test (#2001 )	2026-04-27 05:01:23 -07:00
README.md	chore: final open-source cleanup — binary, stale paths, private refs	2026-04-18 00:38:55 -07:00
test_ci_required_drift.py	feat(internal#219 §4+§6): port ci-required-drift + audit-force-merge sidecar from CP	2026-05-11 00:35:25 -07:00
test_main_red_watchdog.py	feat(ci): main-red watchdog (Option C of main-never-red directive) — closes #420	2026-05-11 00:36:20 -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.