What is the benefit of using the same context and browser instance in Playwright when running multiple tests on a single worker?


Speed Up Your Tests with Playwright

Hey there! If you're running a large number of tests on a single worker with @playwright/test, you can definitely speed things up by reusing the same context and browser instance.

Reusable Contexts

Playwright has this cool feature called "browser contexts". It lets you create isolated browser profiles for each test. So, each test gets its own fresh browser context, free from interference from other tests.

Here's how you can create a new context:

const { chromium } = require('@playwright/test');

const browser = await chromium.launch();
const context = await browser.newContext();

Save Time with Authentication

Playwright lets you save the authentication state of the context and reuse it in all tests. You just need to log in once and then reuse that authenticated state across all your tests. This saves you from having to log in for each test.

Parallel Execution and Sharding

Playwright supports running multiple tests in parallel by default. If you have many independent tests within a single file, consider running them in parallel.

If your test suite is large enough, Playwright also supports sharding. This allows you to split your test suite into multiple parts (shards) so they can be executed simultaneously on different machines or workers.

// playwright.config.ts
import { PlaywrightTestConfig } from '@playwright/test';

const config: PlaywrightTestConfig = {
  // ...
  workers: 2,
  shards: 2,
export default config;

So, by using the same context and browser instance, and leveraging features like reusable contexts and parallel execution, you can make your testing process more efficient and faster. Happy testing!


Thank you!
Was this helpful?
Still have questions?

If you still have questions, please ask a question and I will try to answer it.

Related Discord Threads

Related Questions

AboutQuestionsDiscord ForumBrowser ExtensionTagsQA Jobs

Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email luc@ray.run.