From 154b043d5f0e210bf9bde417638330ac6c743f82 Mon Sep 17 00:00:00 2001 From: notgitika Date: Fri, 1 May 2026 18:53:43 -0400 Subject: [PATCH] fix: use correct resourceType for config bundle in E2E status test The status command outputs resourceType as 'config-bundle' (hyphenated) but the test was checking for 'configBundle' (camelCase). --- e2e-tests/config-bundle-eval-rec.test.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/e2e-tests/config-bundle-eval-rec.test.ts b/e2e-tests/config-bundle-eval-rec.test.ts index c8aac5dec..01e3287bf 100644 --- a/e2e-tests/config-bundle-eval-rec.test.ts +++ b/e2e-tests/config-bundle-eval-rec.test.ts @@ -206,7 +206,7 @@ describe.sequential('e2e: config bundles, batch evaluation, and recommendations' }; expect(json.success).toBe(true); - const bundle = json.resources.find(r => r.resourceType === 'configBundle' && r.name === bundleName); + const bundle = json.resources.find(r => r.resourceType === 'config-bundle' && r.name === bundleName); expect(bundle, `Config bundle "${bundleName}" should appear in status`).toBeDefined(); const evaluator = json.resources.find(r => r.resourceType === 'evaluator' && r.name === evalName);