Playwright testConfig.retryStrategy supports isolated retries
Introduced 2026-07-24 · score 0.98
HOW TO USE IT
When failed tests should run after the rest of the suite, set `retryStrategy: 'isolated'` in the Playwright config; retries then run one by one in a single worker. [Playwright TestConfig](https://playwright.dev/docs/api/class-testconfig#test-config-retry-strategy)
import { defineConfig } from '@playwright/test';
export default defineConfig({
retries: 2,
retryStrategy: 'isolated',
});WHY THIS HELPS
Run failed test retries after the rest of the suite to minimize interference between retries and other tests.
BEFORE THIS CHANGE
The default `'immediate'` strategy retries a failed test as soon as a worker is available, interleaved with the rest of the run.
REQUIREMENTS AND LIMITATIONS
- Version: v1.62.0
- retryStrategy: Controls when failed tests are retried. `'isolated'` runs retries at the end, one by one in a single worker; the default is `'immediate'`.
- retries: Maximum number of retry attempts for failed tests; by default, failing tests are not retried.
- Prerequisite: `retryStrategy` was added in Playwright v1.62.
- `'immediate'` is the default strategy.
- `'isolated'` runs all retries at the end, one by one in a single worker.
FIRST-PARTY EVIDENCE
- https://github.com/microsoft/playwright/releases/tag/v1.62.0
- https://playwright.dev/docs/api/class-testconfig#test-config-retry-strategy
- https://playwright.dev/docs/api/class-testconfig#test-config-retries
Check the installed version and the source before using it. Entry JSON