[BUG] Global options not working with simple test case

Context:

• Playwright Version: 1.21
• Operating System: Linux
• Node.js version: v16.14.1
• Browser: Chromium

System:

• OS: Linux 5.17 openSUSE Tumbleweed 20220404
• Memory: 4.66 GB / 15.29 GB
• Container: Yes

Binaries:

• Node: 16.14.1 - /usr/bin/node
• npm: 8.5.0 - /usr/bin/npm

Languages:

• Bash: 5.1.16 - /usr/bin/bash

Code Snippet

I have the following three files in a src folder:

test-main.test.ts

import { test } from "@playwright/test";

test("basic test", async ({ context }) => {
  const page = await context.newPage();
  await page.goto("https://google.com");
  await page.waitForTimeout(31 * 1000);
});

playwright.config.ts

import { PlaywrightTestConfig } from "@playwright/test";

const config: PlaywrightTestConfig = {
  reporter: "list",
  testDir: "./src",
  timeout: 60 * 1000,
  globalSetup: require.resolve("./global-setup"),
};
export default config;

global-setup.ts

import { chromium, FullConfig } from "@playwright/test";

async function globalSetup(config: FullConfig) {
  const baseURL = "http://google.de//";
  const storageStatepath = "storageState.json";
  const browser = await chromium.launch({ headless: false });
  const page = await browser.newPage();
  await page.goto(baseURL);
  await page.click("#gksS1d");
  await page.fill("#identifierId", id);
  await page.click("#identifierNext");
  await page.fill("#password", password);
  await page.click("#passwordNext");
  await page.context().storageState({ path: storageStatepath });
  await browser.close();
}

export default globalSetup;

Describe the bug

I should not need to authenticate in the test case as I use the global setup to do so (see https://playwright.dev/docs/test-advanced#global-setup-and-teardown). However, the pop up for log in still occur in the test case.

This bug is may be related to https://github.com/microsoft/playwright/issues/13681

[Marcelo00]

Thanks @pavelfeldman 😃

I moved the config file from the src folder to the root folder and it worked as expected. Also the problem with the timeout in #13681 is solved with this small fix.

It would be great if the explanation could be mentioned in the docs.

[Marcelo00]

This unfortunately does not help. I have a simple log statement in the global-setup but it is not printed.

The usage of require.resolve() is also in the docs.