What is the reason for tests failing when using 'await use(page)' in Playwright test runner and how can I fix it?


The Issue with await use(page)

The problem occurs when you use await use(page) within a fixture setup function in @playwright/test. If there are other async operations being performed outside of this call, they may complete before your fixture has finished setting up, leading to unexpected behavior and test failures.

How to Fix It

To fix this issue, ensure that all async operations within your fixture's scope are properly awaited before moving on with subsequent steps in your test. Additionally, make sure that any calls made using use() are properly awaited as well.

Here's an example of a properly awaited fixture setup function:

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

test.describe('ray.run website', () => {
  test.beforeEach(async ({ page }) => {
    await page.goto('https://ray.run/');

  test('Check the title', async ({ page }) => {
    const title = await page.title();
    expect(title).toBe('Ray.run - Playwright Testing');

In this example, we use await page.goto('https://ray.run/') to ensure that the page navigation is completed before moving on to the test.

By properly awaiting all async operations within your fixture and test, you can avoid issues with failing tests when using await use(page) in Playwright test runner.

Thank you!
Was this helpful?
Still have questions?

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

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.