fix(test-runner): warn users who invoke the test-runner with Jest

[Max Schmitt (mxschmitt)]

Relates:

• [Question]: Get test() can only be called in a test file error while I run npx playwright test #7714
• [Bug]: Devops Pipelines/Releases fail to run npx playwright test #7587

See here about the worker-index env var: https://jestjs.io/docs/environment-variables. Its probably the easiest way to detect if its Jest or not.

Before it lead to when using Jest on Playwright tests:

 FAIL tests/foo.spec.js
● Test suite failed to run
test() can only be called in a test file
1 | const { test, expect } = require('@playwright/test');
2 |
> 3 | test('basic test', async ({ page }) => {
| ^
4 | await page.goto('https://playwright.dev/');
5 | const name = await page.innerText('.navbar__title');
6 | expect(name).toBe('Playwright');
at Object.<anonymous> (tests/foo.spec.js:3:1)

Not sure where to put, we can also put it on the top-level at the end of the file.

[Joel Einbinder (JoelEinbinder)]

I agree with dmitry that it's impolite to throw immediately if we detect Jest. Let's just throw a better error message if we detect Jest when we currently throw test() can only be called in a test file.

[Max Schmitt (mxschmitt)]

Relates:

• [Question]: Get test() can only be called in a test file error while I run npx playwright test #7714
• [Bug]: Devops Pipelines/Releases fail to run npx playwright test #7587

See here about the worker-index env var: https://jestjs.io/docs/environment-variables. Its probably the easiest way to detect if its Jest or not.

Before it lead to when using Jest on Playwright tests:

 FAIL tests/foo.spec.js
● Test suite failed to run
test() can only be called in a test file
1 | const { test, expect } = require('@playwright/test');
2 |
> 3 | test('basic test', async ({ page }) => {
| ^
4 | await page.goto('https://playwright.dev/');
5 | const name = await page.innerText('.navbar__title');
6 | expect(name).toBe('Playwright');
at Object.<anonymous> (tests/foo.spec.js:3:1)

Not sure where to put, we can also put it on the top-level at the end of the file.

[Joel Einbinder (JoelEinbinder)]

I agree with dmitry that it's impolite to throw immediately if we detect Jest. Let's just throw a better error message if we detect Jest when we currently throw test() can only be called in a test file.

[Max Schmitt (mxschmitt)]

Relates:

• [Question]: Get test() can only be called in a test file error while I run npx playwright test #7714
• [Bug]: Devops Pipelines/Releases fail to run npx playwright test #7587

See here about the worker-index env var: https://jestjs.io/docs/environment-variables. Its probably the easiest way to detect if its Jest or not.

Before it lead to when using Jest on Playwright tests:

 FAIL tests/foo.spec.js
● Test suite failed to run
test() can only be called in a test file
1 | const { test, expect } = require('@playwright/test');
2 |
> 3 | test('basic test', async ({ page }) => {
| ^
4 | await page.goto('https://playwright.dev/');
5 | const name = await page.innerText('.navbar__title');
6 | expect(name).toBe('Playwright');
at Object.<anonymous> (tests/foo.spec.js:3:1)

Not sure where to put, we can also put it on the top-level at the end of the file.

[Joel Einbinder (JoelEinbinder)]

I agree with dmitry that it's impolite to throw immediately if we detect Jest. Let's just throw a better error message if we detect Jest when we currently throw test() can only be called in a test file.

[Max Schmitt (mxschmitt)]

Relates:

• [Question]: Get test() can only be called in a test file error while I run npx playwright test #7714
• [Bug]: Devops Pipelines/Releases fail to run npx playwright test #7587

See here about the worker-index env var: https://jestjs.io/docs/environment-variables. Its probably the easiest way to detect if its Jest or not.

Before it lead to when using Jest on Playwright tests:

 FAIL tests/foo.spec.js
● Test suite failed to run
test() can only be called in a test file
1 | const { test, expect } = require('@playwright/test');
2 |
> 3 | test('basic test', async ({ page }) => {
| ^
4 | await page.goto('https://playwright.dev/');
5 | const name = await page.innerText('.navbar__title');
6 | expect(name).toBe('Playwright');
at Object.<anonymous> (tests/foo.spec.js:3:1)

Not sure where to put, we can also put it on the top-level at the end of the file.

[Joel Einbinder (JoelEinbinder)]

I agree with dmitry that it's impolite to throw immediately if we detect Jest. Let's just throw a better error message if we detect Jest when we currently throw test() can only be called in a test file.

[Max Schmitt (mxschmitt)]

Relates:

• [Question]: Get test() can only be called in a test file error while I run npx playwright test #7714
• [Bug]: Devops Pipelines/Releases fail to run npx playwright test #7587

See here about the worker-index env var: https://jestjs.io/docs/environment-variables. Its probably the easiest way to detect if its Jest or not.

Before it lead to when using Jest on Playwright tests:

 FAIL tests/foo.spec.js
● Test suite failed to run
test() can only be called in a test file
1 | const { test, expect } = require('@playwright/test');
2 |
> 3 | test('basic test', async ({ page }) => {
| ^
4 | await page.goto('https://playwright.dev/');
5 | const name = await page.innerText('.navbar__title');
6 | expect(name).toBe('Playwright');
at Object.<anonymous> (tests/foo.spec.js:3:1)

Not sure where to put, we can also put it on the top-level at the end of the file.

[Joel Einbinder (JoelEinbinder)]

I agree with dmitry that it's impolite to throw immediately if we detect Jest. Let's just throw a better error message if we detect Jest when we currently throw test() can only be called in a test file.

[Max Schmitt (mxschmitt)]

Relates:

• [Question]: Get test() can only be called in a test file error while I run npx playwright test #7714
• [Bug]: Devops Pipelines/Releases fail to run npx playwright test #7587

See here about the worker-index env var: https://jestjs.io/docs/environment-variables. Its probably the easiest way to detect if its Jest or not.

Before it lead to when using Jest on Playwright tests:

 FAIL tests/foo.spec.js
● Test suite failed to run
test() can only be called in a test file
1 | const { test, expect } = require('@playwright/test');
2 |
> 3 | test('basic test', async ({ page }) => {
| ^
4 | await page.goto('https://playwright.dev/');
5 | const name = await page.innerText('.navbar__title');
6 | expect(name).toBe('Playwright');
at Object.<anonymous> (tests/foo.spec.js:3:1)

Not sure where to put, we can also put it on the top-level at the end of the file.

[Joel Einbinder (JoelEinbinder)]

I agree with dmitry that it's impolite to throw immediately if we detect Jest. Let's just throw a better error message if we detect Jest when we currently throw test() can only be called in a test file.

[Max Schmitt (mxschmitt)]

Relates:

• [Question]: Get test() can only be called in a test file error while I run npx playwright test #7714
• [Bug]: Devops Pipelines/Releases fail to run npx playwright test #7587

See here about the worker-index env var: https://jestjs.io/docs/environment-variables. Its probably the easiest way to detect if its Jest or not.

Before it lead to when using Jest on Playwright tests:

 FAIL tests/foo.spec.js
● Test suite failed to run
test() can only be called in a test file
1 | const { test, expect } = require('@playwright/test');
2 |
> 3 | test('basic test', async ({ page }) => {
| ^
4 | await page.goto('https://playwright.dev/');
5 | const name = await page.innerText('.navbar__title');
6 | expect(name).toBe('Playwright');
at Object.<anonymous> (tests/foo.spec.js:3:1)

Not sure where to put, we can also put it on the top-level at the end of the file.

[Joel Einbinder (JoelEinbinder)]

I agree with dmitry that it's impolite to throw immediately if we detect Jest. Let's just throw a better error message if we detect Jest when we currently throw test() can only be called in a test file.