playwright-fixtures-and-hooks

Playwright fixtures enable you to define reusable setup and teardown logic shared across tests. Create custom fixtures by declaring them in your configuration, specify their scope (test or worker), and use them as function parameters in your tests to automate state management and initialization.

Test-scoped fixtures run before and after each individual test, isolating state per test. Worker-scoped fixtures run once per worker process, reducing overhead for expensive setup like browser instances. Choose test scope for isolation and worker scope for performance when state can be safely shared.

Yes, fixtures support authentication flows by enabling you to store login state, manage cookies, and set storage state once, then reuse authenticated context across multiple tests. This eliminates redundant login steps and accelerates test execution while maintaining consistent session management.

Fixtures provide built-in context and browser fixtures that let you configure permissions, manage page navigation, and control browser behavior before tests run. Custom fixtures extend these to encapsulate complex setup like granting geolocation or camera permissions across your test suite.

Fixtures apply across all Playwright test types—unit, integration, and end-to-end. They standardize setup and teardown logic regardless of test scope, enabling consistent resource management and state handling across your entire test suite.

Yes, fixtures include a built-in request fixture for HTTP calls. You can create custom fixtures that set up API contexts, manage authentication tokens, or seed data via API before UI tests run, integrating API automation into your fixture lifecycle.