Fixtures

Playwright Test is based on the concept of the test fixtures. Test fixtures are used to establish environment for each test, giving the test everything it needs and nothing else.

Playwright Test looks at each test declaration, analyses the set of fixtures the test needs and prepares those fixtures specifically for the test. Values prepared by the fixtures are merged into a single object that is available to the test, hooks, annotations and other fixtures as a first parameter.

TypeScript

import { test, expect } from '@playwright/test';

test('basic test', async ({ page }) => {
  // ...
});

JavaScript

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

test('basic test', async ({ page }) => {
  // ...
});

Given the test above, Playwright Test will set up the page fixture before running the test, and tear it down after the test has finished. page fixture provides a Page object that is available to the test.

Playwright Test comes with builtin fixtures listed below, and you can add your own fixtures as well. Playwright Test also provides options to configure fixtures.browser, fixtures.context and fixtures.page.

• fixtures.browser
• fixtures.browserName
• fixtures.context
• fixtures.page
• fixtures.request

fixtures.browser

Added in: v1.10

• type: <Browser>

Browser instance is shared between all tests in the same worker - this makes testing efficient. However, each test runs in an isolated BrowserContext and gets a fresh environment.

Learn how to configure browser and see available options.

fixtures.browserName

Added in: v1.10

• type: <"chromium"|"firefox"|"webkit">

Name of the browser that runs tests. Defaults to 'chromium'. Useful to annotate tests based on the browser.

TypeScript

test('skip this test in Firefox', async ({ page, browserName }) => {
  test.skip(browserName === 'firefox', 'Still working on it');
  // ...
});

JavaScript

test('skip this test in Firefox', async ({ page, browserName }) => {
  test.skip(browserName === 'firefox', 'Still working on it');
  // ...
});

fixtures.context

Added in: v1.10

• type: <BrowserContext>

Isolated BrowserContext instance, created for each test. Since contexts are isolated between each other, every test gets a fresh environment, even when multiple tests run in a single Browser for maximum efficiency.

Learn how to configure context and see available options.

Default fixtures.page belongs to this context.

fixtures.page

Added in: v1.10

• type: <Page>

Isolated Page instance, created for each test. Pages are isolated between tests due to fixtures.context isolation.

This is the most common fixture used in a test.

TypeScript

import { test, expect } from '@playwright/test';

test('basic test', async ({ page }) => {
  await page.goto('/signin');
  await page.getByLabel('User Name').fill('user');
  await page.getByLabel('Password').fill('password');
  await page.getByText('Sign in').click();
  // ...
});

JavaScript

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

test('basic test', async ({ page }) => {
  await page.goto('/signin');
  await page.getByLabel('User Name').fill('user');
  await page.getByLabel('Password').fill('password');
  await page.getByText('Sign in').click();
  // ...
});

fixtures.request

Added in: v1.10

• type: <APIRequestContext>

Isolated APIRequestContext instance for each test.

TypeScript

import { test, expect } from '@playwright/test';

test('basic test', async ({ request }) => {
  await request.post('/signin', {
    data: {
      username: 'user',
      password: 'password'
    }
  });
  // ...
});

JavaScript

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

test('basic test', async ({ request }) => {
  await request.post('/signin', {
    data: {
      username: 'user',
      password: 'password'
    }
  });
});