mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-08-26 00:52:18 +03:00
65e81158ab
Landed with the design call resolved per the owner's pick — **option 1**: the synced store is now endpoint-agnostic (persistDiscoveredModels and managedModelImport no longer drop non-chat models at write time), and chat selectability moved to read time (auto-pool expansion in autoStrategy applies filterChatSelectableModels; the models-route projection already had its chatOnly filter). Your discovery test now passes end-to-end (3/3): /api/show capabilities persist per connection and image/embedding requests route through the advertising host. Reconciliation notes: conflicted areas merged onto the current tip (adobe discovery import, requestedModel preflight signature, resolvedProvider fast-path coexists with the synced-route override — explicit resolution wins); carried base-red drains (#10055 memoization, #11071 test variants) dropped as already-landed; the managed-model-import exclusion test was propagated to the new contract (image/video models persist; the read filter still hides them from chat pickers — pinned by a new assertion). Full battery: 205/206 focused (the one red is a confirmed periodic-timer timing flake on the loaded devbox — 20/20 isolated), autoCombo vitest 30/30, combo suites 46/46, gates + typecheck clean. Thank you @yourspraveen — the capability probe + routing design was right; it just needed the store contract opened up. Fixes #11087.
42 lines
1.8 KiB
TypeScript
42 lines
1.8 KiB
TypeScript
import { defineConfig } from "vitest/config";
|
|
import path from "path";
|
|
|
|
/**
|
|
* Live-server E2E suites (`tests/e2e/ecosystem.test.ts`,
|
|
* `tests/e2e/protocol-clients.test.ts`).
|
|
*
|
|
* These are the only two suites that drive a REAL running OmniRoute over HTTP
|
|
* rather than importing modules. Their runners — `scripts/dev/run-ecosystem-tests.mjs`
|
|
* and `scripts/dev/run-protocol-clients-tests.mjs` — boot a dev server, wait for
|
|
* `/api/monitoring/health`, then invoke Vitest with this config.
|
|
*
|
|
* They need their own config because `vitest.config.ts` deliberately EXCLUDES both
|
|
* files (they must not run in the jsdom UI job, which has no server). Since the
|
|
* runners previously invoked Vitest with no `--config`, they loaded that default
|
|
* config and the exclusion discarded the very file passed as the positional filter —
|
|
* so both scripts failed with "No test files found, exiting with code 1" and neither
|
|
* suite had a way to execute.
|
|
*/
|
|
export default defineConfig({
|
|
test: {
|
|
// Real HTTP against a running server — never jsdom.
|
|
environment: "node",
|
|
globals: true,
|
|
include: ["tests/e2e/ecosystem.test.ts", "tests/e2e/protocol-clients.test.ts"],
|
|
exclude: ["**/node_modules/**", "**/.git/**"],
|
|
// Both suites share ONE server instance, so files must not run concurrently.
|
|
fileParallelism: false,
|
|
// Upstream calls over the network are slower than in-process unit tests; the
|
|
// suites themselves also read ECOSYSTEM_*_TIMEOUT_MS for their per-case budgets.
|
|
testTimeout: 60000,
|
|
hookTimeout: 60000,
|
|
},
|
|
resolve: {
|
|
alias: {
|
|
"@": path.resolve(__dirname, "./src"),
|
|
// Mirrors tsconfig paths, same as the other two vitest configs.
|
|
"@omniroute/open-sse": path.resolve(__dirname, "./open-sse"),
|
|
},
|
|
},
|
|
});
|