Playwright Test runs tests in worker processes. These processes are OS processes, running independently, orchestrated by the test runner. All workers have identical environments and each starts its own browser.
When **all tests pass**, they will run in order in the same worker process.
* Worker process starts
*`first good` passes
*`second flaky` passes
*`third good` passes
Should **any test fail**, Playwright Test will discard the entire worker process along with the browser and will start a new one. Testing will continue in the new worker process starting with the next test.
* Worker process #1 starts
*`first good` passes
*`second flaky` fails
* Worker process #2 starts
*`third good` passes
If you **enable [retries](#retries)**, second worker process will start by retrying the failed test and continue from there.
* Worker process #1 starts
*`first good` passes
*`second flaky` fails
* Worker process #2 starts
*`second flaky` is retried and passes
*`third good` passes
This scheme works perfectly for independent tests and guarantees that failing tests can't affect healthy ones.
## Retries
Playwright Test supports **test retries**. When enabled, failing tests will be retried multiple times until they pass, or until the maximum number of retries is reached.
Use [`method: Test.describe.serial`] to group dependent tests to ensure they will always run together and in order. If one of the tests fails, all subsequent tests are skipped. All tests in the group are retried together.
Consider the following snippet that uses `test.describe.serial`:
When running without [retries](#retries), all tests after the failure are skipped:
* Worker process #1:
*`first good` passes
*`second flaky` fails
*`third good` is skipped entirely
When running with [retries](#retries), all tests are retried together:
* Worker process #1:
*`first good` passes
*`second flaky` fails
*`third good` is skipped
* Worker process #2:
*`first good` passes again
*`second flaky` passes
*`third good` passes
:::note
It is usually better to make your tests isolated, so they can be efficiently run and retried independently.
:::
## Reuse single page between tests
Playwright Test creates an isolated [Page] object for each test. However, if you'd like to reuse a single [Page] object between multiple tests, you can create your own in [`method: Test.beforeAll`] and close it in [`method: Test.afterAll`].