Playwright: Test timeout of 30000ms exceeded

Playwright Test gives every test, including its beforeEach and afterEach hooks and fixtures, 30 seconds by default. When that budget runs out, the runner aborts the test and reports this message. Because actions in Playwright Test have no separate timeout by default, a single click waiting on an element that never becomes actionable will often consume the whole test budget, and the error you see is this one rather than an action timeout.

The runner usually prints a second error below it, for example the action that was still pending or Target page, context or browser has been closed because the page was torn down mid-action. That second error and its call log tell you where the time went.

What is not wrong: the 30-second value is a default, not a limit imposed by the browser. Long end-to-end flows legitimately need more.

// playwright.config.ts
export default defineConfig({
  timeout: 60_000,
  expect: { timeout: 10_000 },
  use: { actionTimeout: 15_000, navigationTimeout: 30_000 },
});

// In a single long test
test('exports a large report', async ({ page }) => {
  test.slow();
  // ...
});

Give actions their own timeout so the test timeout is a safety net, not the first signal. Keep authentication and seeding out of individual tests with setup projects and storageState. Watch per-test duration in reports; a test that creeps toward the limit is a flaky test waiting to happen.