## What `full-suite.yml` shard 1 on main fails with **zero test failures** — it dies on a resolution error: ``` Failed to resolve import "@fusion/core/task-delete-attribution" from "packages/dashboard/app/api/client.ts" ``` **Root cause.** Vite string aliases match by **PREFIX**. So `find: "@fusion/core"` → `core/src/index.ts` rewrites `@fusion/core/task-delete-attribution` into `core/src/index.ts/task-delete-attribution`, which cannot resolve. The narrower subpath alias has to come *first*. The module exists and *is* correctly declared in `packages/core/package.json` exports — this is purely a test-config trap, and `packages/dashboard/vitest.config.ts` already documents it in a comment. Six configs alias `@fusion/dashboard` (whose `app/api/client.ts` imports that browser-safe leaf) while lacking the narrower alias, so they inherited the trap. This carries the same one-line pattern to all six. ## Measured `dependency-graph` — the project actually red on main: | | Test files | Tests collected | |---|---|---| | before | 3 failed \| 17 passed | 147 | | after | **20 passed** | **180** | **33 tests were never collected** — neither passing nor reported as failing. That is the part worth flagging: an unresolved import removes tests from the run silently, and the shard's own summary printed no `Tests N failed` line at all, which is why this red looked like infrastructure noise rather than a real defect. No regressions: `reports` 110, `cli-printing-press` 41, `compound-engineering` 317, **gate 726** — all green. `pnpm lint` clean. `@fusion/desktop` is `1 failed | 264 passed` **both before and after**; verified pre-existing on clean `origin/main` by reverting just that one config and re-running. Cause is `@fusion-plugin-examples/roadmap` entry resolution, unrelated — **flagged, not fixed.** ## Deliberately not changed Engine's *second* `@fusion/core` alias (the `.gate-bundle/core.mjs` entry) is untouched: that lane bundles core on purpose, and pointing it at source would defeat the isolation the gate bundle exists to provide. ## Full-suite triage this came out of (for whoever owns the rest) Reading the four red shards of the last completed run on main (`30523568756`): | Shard | Real cause | Owner | |---|---|---| | 1/4 | **this PR** — resolution error, 0 test failures | — | | 2/4 | 23 failed: `store-wedge-resolution.pg`, `central-archive-secrets`, `task-delete-caller-attribution`, `task-delete-nonblocking-cleanup` | #2669 / #2675 cover the first two | | 3/4 | **watchdog SIGKILL** mid-`@fusion/engine [1/2]` — no test failures, no summary | unowned | | 4/4 | 17 failed, all in `@runfusion/fusion` CLI (`project.test.ts` 8, `task.test.ts` 5, `extension.test.ts` 2, +2) | unowned | Two of the four shard reds contain **no failing test at all**, so "main's full-suite failure count" cannot be read off the shard conclusions — it has to be read off `Tests N failed` summary lines, and shards 1 and 3 emit none.
135 lines
6.7 KiB
TypeScript
135 lines
6.7 KiB
TypeScript
import { defineConfig } from "vitest/config";
|
|
import { fileURLToPath } from "node:url";
|
|
import { computeMaxWorkers } from "../../packages/core/src/__test-utils__/vitest-workers";
|
|
|
|
const maxWorkers = computeMaxWorkers();
|
|
|
|
/*
|
|
FNXC:CompoundEngineeringTests 2026-06-17-17:02:
|
|
Direct CE plugin test commands must behave like the central pnpm test runner even when the caller's shell exports NODE_ENV=production. Force test mode before Vitest resolves React Testing Library so jsdom tests use React's act-capable test path.
|
|
*/
|
|
process.env.NODE_ENV = "test";
|
|
|
|
const coreSetup = fileURLToPath(
|
|
new URL("../../packages/core/src/__test-utils__/vitest-setup.ts", import.meta.url),
|
|
);
|
|
const dashboardSetup = fileURLToPath(new URL("./src/dashboard/test-setup.ts", import.meta.url));
|
|
|
|
/*
|
|
FNXC:CompoundEngineeringTests 2026-06-17-12:35:
|
|
FN-6587 quarantines the CE broad-pnpm-test timeout flakes without timeout appeasement. Keep these excludes mirrored in scripts/lib/test-quarantine.json and remove or delete the files when the 14-day ratchet resolves.
|
|
|
|
FNXC:CompoundEngineeringTests 2026-06-17-16:20:
|
|
FN-6593 deletes orchestrator-flow.test.ts and skill-wiring.test.ts under the ratchet because the broad-workflow-only 5000ms timeout could not be tied to a narrow non-appeasement root cause.
|
|
Keep the ledger entries and excludes removed together; git history remains the archive for this dropped CE orchestrator/skill-wiring coverage.
|
|
|
|
FNXC:CompoundEngineeringTests 2026-06-17-19:56:
|
|
FN-6606 re-ran the loaded CE node/package lane with sync.test.ts and work-bridge.test.ts temporarily unexcluded and could not reproduce either the 5000ms test timeout or the later 10000ms hook timeout.
|
|
The current HEAD's shared test-isolation fixes now keep the broad lane stable, so restore both files to active coverage and clear the stale quarantine in lockstep with scripts/lib/test-quarantine.json.
|
|
|
|
FNXC:CompoundEngineeringTests 2026-07-13-22:37:
|
|
The PostgreSQL session-store port uses getAsyncLayer with a safe SQLite fallback, so the six session/orchestrator files previously excluded for stale TaskStore mocks are active coverage again. The quarantine ledger contains no matching entries; configuration and coverage must remain aligned.
|
|
*/
|
|
const nodeOnlyDashboardTests = [
|
|
"src/dashboard/__tests__/theme-tokens.test.ts",
|
|
];
|
|
|
|
export default defineConfig({
|
|
resolve: {
|
|
alias: [
|
|
{
|
|
find: /^@fusion-plugin-examples\/compound-engineering\/dashboard-view$/,
|
|
replacement: fileURLToPath(new URL("./src/dashboard-view.tsx", import.meta.url)),
|
|
},
|
|
{
|
|
find: /^@fusion-plugin-examples\/compound-engineering$/,
|
|
replacement: fileURLToPath(new URL("./src/index.ts", import.meta.url)),
|
|
},
|
|
/*
|
|
FNXC:VitestAliases 2026-07-30-13:10:
|
|
Must precede the broader `@fusion/core` alias: Vite string aliases match by PREFIX, so that key
|
|
rewrites this subpath to `index.ts/task-delete-attribution` and resolution fails. Reached here
|
|
transitively — this project aliases `@fusion/dashboard`, and `app/api/client.ts` imports the
|
|
browser-safe delete-attribution leaf.
|
|
*/
|
|
{ find: "@fusion/core/task-delete-attribution", replacement: fileURLToPath(new URL("../../packages/core/src/task-delete-attribution.ts", import.meta.url)) },
|
|
{ find: "@fusion/core", replacement: fileURLToPath(new URL("../../packages/core/src/index.ts", import.meta.url)) },
|
|
{
|
|
find: "@fusion/test-utils/pg-test-harness",
|
|
replacement: fileURLToPath(new URL("../../packages/core/src/__test-utils__/pg-test-harness.ts", import.meta.url)),
|
|
},
|
|
{
|
|
find: "@fusion/plugin-sdk",
|
|
replacement: fileURLToPath(new URL("../../packages/plugin-sdk/src/index.ts", import.meta.url)),
|
|
},
|
|
{ find: "@fusion/dashboard", replacement: fileURLToPath(new URL("../../packages/dashboard", import.meta.url)) },
|
|
{
|
|
find: "lucide-react",
|
|
replacement: fileURLToPath(new URL("../../packages/dashboard/node_modules/lucide-react", import.meta.url)),
|
|
},
|
|
],
|
|
},
|
|
test: {
|
|
globalSetup: [fileURLToPath(new URL("../../packages/core/src/__test-utils__/vitest-teardown.ts", import.meta.url))],
|
|
pool: "threads",
|
|
maxWorkers,
|
|
minWorkers: 1,
|
|
/*
|
|
FNXC:PluginPgTestTimeout 2026-07-23-22:15:
|
|
The shared PG test harness (packages/core/src/__test-utils__/pg-test-harness.ts) pays its
|
|
golden-schema-template cold start inside the FIRST pg test of a vitest invocation, which is
|
|
budgeted for the 15s testTimeout its home package (@fusion/core) configures. Plugin packages
|
|
ran at vitest's 5s default, so the whatsapp-chat persistence.pg.test.ts timed out on loaded
|
|
CI runners (full-suite shard 4, 2026-07-24). Align every pg-harness-consuming plugin with
|
|
core's budget.
|
|
*/
|
|
testTimeout: 15_000,
|
|
projects: [
|
|
{
|
|
extends: true,
|
|
test: {
|
|
name: "compound-engineering-dashboard",
|
|
environment: "jsdom",
|
|
include: ["src/dashboard/**/__tests__/**/*.test.{ts,tsx}", "src/dashboard/**/*.test.{ts,tsx}"],
|
|
exclude: nodeOnlyDashboardTests,
|
|
globalSetup: [],
|
|
/*
|
|
FNXC:CompoundEngineeringTests 2026-06-17-16:50:
|
|
Dashboard tests run in jsdom and must not inherit the core Node-only isolation setup. That setup imports node:module/node:worker_threads and makes Vite externalize built-ins during browser-style setup, which regressed the CE test lane into slow startup followed by ERR_UNKNOWN_BUILTIN_MODULE.
|
|
|
|
FNXC:CompoundEngineeringTests 2026-06-17-16:54:
|
|
File-inspection dashboard tests that read CSS from disk are Node tests even though they live beside React tests. Keep them out of the jsdom project so fs/path/url imports are not browser-externalized.
|
|
|
|
FNXC:CompoundEngineeringTests 2026-06-17-17:10:
|
|
Projects that do not run the core isolation setup must not inherit its global teardown. Otherwise a completed dashboard project can remove FUSION_TEST_WORKER_ROOT while the CE Node project is still redirecting tmpdir writes there.
|
|
*/
|
|
setupFiles: [dashboardSetup],
|
|
},
|
|
},
|
|
{
|
|
extends: true,
|
|
test: {
|
|
name: "compound-engineering-node",
|
|
environment: "node",
|
|
include: ["src/**/__tests__/**/*.test.{ts,tsx}", "src/**/*.test.{ts,tsx}"],
|
|
setupFiles: [coreSetup],
|
|
exclude: [
|
|
"src/dashboard/**/__tests__/**/*.test.{ts,tsx}",
|
|
"src/dashboard/**/*.test.{ts,tsx}",
|
|
],
|
|
},
|
|
},
|
|
{
|
|
extends: true,
|
|
test: {
|
|
name: "compound-engineering-dashboard-node",
|
|
environment: "node",
|
|
include: nodeOnlyDashboardTests,
|
|
globalSetup: [],
|
|
setupFiles: [],
|
|
},
|
|
},
|
|
],
|
|
},
|
|
});
|