From 485fe4ba1c5878083c6e2b6a2d98b37208772a1f Mon Sep 17 00:00:00 2001 From: Tam Nhu Tran Date: Sun, 19 Apr 2026 15:27:24 -0400 Subject: [PATCH] test(cliproxy): assert routing persistence via unified config loader MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The previous assertion read the generated CLIProxy config.yaml directly via getConfigPathForPort(). On the self-hosted CI runner this produced ENOENT even though applyCliproxyRoutingStrategy returned 'config-only', indicating the read path and write path diverged in the full test-suite context. Verify persistence via loadUnifiedConfig() instead — that's the canonical source mutateUnifiedConfig writes to, independent of regenerateConfig's file-path resolution. --- tests/unit/cliproxy/routing-strategy.test.ts | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/tests/unit/cliproxy/routing-strategy.test.ts b/tests/unit/cliproxy/routing-strategy.test.ts index 187ab5cd..3a195e14 100644 --- a/tests/unit/cliproxy/routing-strategy.test.ts +++ b/tests/unit/cliproxy/routing-strategy.test.ts @@ -116,11 +116,9 @@ describe('cliproxy routing strategy service', () => { expect(result.applied).toBe('config-only'); expect(result.strategy).toBe('fill-first'); - const { getConfigPathForPort } = await import('../../../src/cliproxy/config/path-resolver'); - const configPath = getConfigPathForPort(routingTarget.port); - const configContent = fs.readFileSync(configPath, 'utf8'); - expect(configContent).toContain('routing:'); - expect(configContent).toContain('strategy: fill-first'); + const { loadUnifiedConfig } = await import('../../../src/config/unified-config-loader'); + const persisted = loadUnifiedConfig(); + expect(persisted?.cliproxy?.routing?.strategy).toBe('fill-first'); }); });