From 155f6beb3fe1bd6d0f3f9c61239de0d114709b88 Mon Sep 17 00:00:00 2001 From: you Date: Sun, 29 Mar 2026 17:11:17 +0000 Subject: [PATCH] test: remove Node-specific perf test that fails against Go server The test 'Node perf page should NOT show Go Runtime section' asserts Node.js-specific behavior, but E2E tests now run against the Go server (per this PR), so Go Runtime info is correctly present. Remove the now-irrelevant assertion. --- test-e2e-playwright.js | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/test-e2e-playwright.js b/test-e2e-playwright.js index ef9a6ea..dc5529e 100644 --- a/test-e2e-playwright.js +++ b/test-e2e-playwright.js @@ -840,17 +840,7 @@ async function run() { assert(content.length > 10, 'Perf content should still be present after refresh'); }); - // Test: Node.js perf page shows Event Loop metrics (not Go Runtime) - await test('Perf page shows Event Loop on Node server', async () => { - const perfText = await page.$eval('#perfContent', el => el.textContent); - // Node.js server should show Event Loop metrics - const hasEventLoop = perfText.includes('Event Loop') || perfText.includes('event loop'); - const hasMemory = perfText.includes('Memory') || perfText.includes('RSS'); - assert(hasEventLoop || hasMemory, 'Node perf page should show Event Loop or Memory metrics'); - // Should NOT show Go Runtime section on Node.js server - const hasGoRuntime = perfText.includes('Go Runtime'); - assert(!hasGoRuntime, 'Node perf page should NOT show Go Runtime section'); - }); + // Test: Go perf page shows Go Runtime section (goroutines, GC) // NOTE: This test requires GO_BASE_URL pointing to Go staging (port 82)