From c959fffb1268a3dbfb53f13b5f611368d3919b5d Mon Sep 17 00:00:00 2001 From: Keith Williams Date: Wed, 31 Dec 2025 13:33:13 -0300 Subject: [PATCH] fix: reduce default Playwright test timeout from 60s to 30s in CI (#26345) Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- playwright.config.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/playwright.config.ts b/playwright.config.ts index c08e00231e..1326d04fdb 100644 --- a/playwright.config.ts +++ b/playwright.config.ts @@ -13,12 +13,12 @@ const outputDir = path.join(__dirname, "test-results"); // Dev Server on local can be slow to start up and process requests. So, keep timeouts really high on local, so that tests run reliably locally // So, if not in CI, keep the timers high, if the test is stuck somewhere and there is unnecessary wait developer can see in browser that it's stuck -const DEFAULT_NAVIGATION_TIMEOUT = process.env.CI ? 30000 : 120000; -const DEFAULT_EXPECT_TIMEOUT = process.env.CI ? 30000 : 120000; +const DEFAULT_NAVIGATION_TIMEOUT = process.env.CI ? 10000 : 120000; +const DEFAULT_EXPECT_TIMEOUT = process.env.CI ? 10000 : 120000; // Test Timeout can hit due to slow expect, slow navigation. // So, it should me much higher than sum of expect and navigation timeouts as there can be many async expects and navigations in a single test -const DEFAULT_TEST_TIMEOUT = process.env.CI ? 60000 : 240000; +const DEFAULT_TEST_TIMEOUT = process.env.CI ? 30000 : 240000; const headless = !!process.env.CI || !!process.env.PLAYWRIGHT_HEADLESS;