The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.
TypeScript 3d-modelingagent-frameworkagent-harnessai-agentscadclaude-codecodexcoding-agentsdeveloper-toolsesp32game-developmentmcp-servermulti-agentopen-hardwareopencodeopenharnesspcbroboticsterminaltmux
ci(backend): backend PR CI runs the whole backend unit suite, not only the desk test (#1928)
0xken155f96aad897ca
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.ymlindex 10afe0f64..33a91b152 100644--- a/.github/workflows/ci.yml+++ b/.github/workflows/ci.yml@@ -364,8 +364,10 @@ jobs:cache: npmcache-dependency-path: backend/package-lock.json- run: npm ci --no-audit --no-fund- - name: Shared desk layout compatibility- run: npm test -- src/routes/desk.test.ts+ # The whole backend unit suite (src/**/*.test.ts, including the shared desk layout test): it once ran only the desk+ # test, and main broke 48 team-session tests unseen (#1926).+ - name: Backend unit suite+ run: npm testwebsite-checks:concurrency:diff --git a/docs/validation-and-release.md b/docs/validation-and-release.mdindex 1cb1adb1c..50d61dc04 100644--- a/docs/validation-and-release.md+++ b/docs/validation-and-release.md@@ -35,7 +35,8 @@ PR CI is deliberately fast. Each changed component runs only its own Linux suite| `desktop/` | `desktop-tests` (VM suite, four Linux shards) | 5–7 min || `tui/`, `term/` (the TUI builds on it) | `tui-test` (`cargo test`) | a few minutes || `pty/`, `term/`, `tui/vendor/`, the CLI's ptyhost backend (`cli/src/lib/ptyHost/`, `ptyHostBackend*`, `terminalBackend.contract.ts`) | `pty-checks` (`cargo test` for `term` and `pty`, then the ptyhost terminal contract against the built host) | a few minutes |-| `backend/`, `companions/`, `website/`, `os/`, `provider/`, `mobile/`, `daemons/` | that component's one check | 1–4 min |+| `backend/` | `backend-desk` (the backend unit suite, `npm test` in `backend/`) | about 1–2 min |+| `companions/`, `website/`, `os/`, `provider/`, `mobile/`, `daemons/` | that component's one check | 1–4 min || `devices/` | `firmware-checks` | 1–2 min || `devices/harness-pro/` | also `pro-firmware-build` (ESP-IDF v5.5.4 build of `harness_pro.bin`, which must fit `ota_0`) and `pro-golden` (`test/golden.sh --check` with Liberation Sans, on macOS arm64 where the baseline is recorded: float maths in the code-drawn shapes differs on Linux x86-64) | build ~4 min, golden ~1 min || anything else (docs, workflows, scripts, store) | `process-checks` only | about 1.5 min |