[Bug]: PlayWright extension for VSCode showing 'no tests have been found'

[hgargova]

Version

1.58.0

Steps to reproduce

System info

• OS: Windows 11 (OS: Windows_NT x64 10.0.26200)
• VS Code version: issue is present with 1.114.0, 1.115.0, 1.116.0
• Playwright version: (1.58.0)
• Playwright VS Code extension version: 1.1.17

Describe the bug

Playwright VS Code extension fails to load tests and shows errors in playwright.config.ts, even though everything works correctly from CLI.
In Testing tab:

• No tests are shown
  In editor:
• playwright.config.ts shows error:
  connect ETIMEDOUT ::1:<port> playwright
  In Developer Tools console:
  [ms-playwright.playwright] Illegal argument: character must be non-negative

Steps to reproduce

1. Create a clean project:
   mkdir pw-smoke
   cd pw-smoke
   npm init -y
   npm i -D @playwright/test
   npx playwright install

2. Create playwright.config.ts:

import { defineConfig } from '@playwright/test';
export default defineConfig({
  testDir: './tests',
});
Create tests/smoke.spec.ts:
import { test, expect } from '@playwright/test';
test('smoke', async ({ page }) => {
  await page.goto('https://example.com');
  await expect(page).toHaveTitle(/Example/);
});
Open project in VS Code
Install Playwright extension

### Expected behavior

Expected behavior
Tests should appear in Testing tab
No errors in playwright.config.ts


### Actual behavior

Actual behavior
No tests in Testing tab
Editor shows connect ETIMEDOUT ::1:<port>
Extension crashes with:
Illegal argument: character must be non-negative


### Additional context

Additional info
npx playwright test --list works correctly
Tests run successfully from CLI
Disabling Playwright extension removes the error in the editor
Issue reproduces even in a clean project
Reinstalling VS Code and extension does not fix the issue

### Environment

```shell
System:
OS: Windows 11 Enterprise 10.0.26200
CPU: (18) x64

Binaries:
Node: 20.20.0 - C:\nvm4w\nodejs\node.exe
npm: 10.8.2 - C:\nvm4w\nodejs\npm.cmd

npmPackages:
@playwright/test: 1.58.0

[yury-s]

I can't reproduce it with this project:

[flexeter]

I can reproduce it also.

VS Code - 1.115.0
Playwright Plugin - 1.17.0
PW - 1.57.0
Node - 22.13.1
npm - 11.12.0
OS: Windows 11 Home, Version 25H2, OS Build: 26200.8246

[hgargova]

The issue appeared after a Windows update. The project described shows that even with the simplest project the tests aren't present in the extension.
OS: Windows 11 (OS: Windows_NT x64 10.0.26200)
Edition Windows 11 Enterprise
Version 25H2
OS build 26200.8246

[harorri]

I have the same problem.
When i click in extensions > Playwright Test for VSCode, i see errors in runtime status

[SamuelNCarvalho]

The same issue here.

OS: Windows 11
Edition Windows 11 Business
Version 25H2
OS build 26200.8246

[lucsoft]

Same issues with the newest Windows Update.

It still works fine on macOS

[IvanQL]

I’m experiencing the same issue after the last Windows update. Is there a workaround?

[MateuszKujawa]

I'm experiencing the exact same issue.

Environment:

• OS: Windows 11
• VSCode: 1.116.0
• Playwright: 1.58.2
• Playwright VSCode extension: 1.1.17
• Node.js: 22.18.0

Symptoms:

• playwright.config.ts shows error: connect ETIMEDOUT 127.0.0.1:<port> playwright
• Developer Tools console shows: Illegal argument: character must be non-negative
• No tests appear in the Testing tab
• CLI works perfectly (npx playwright test runs all tests without issues)
• Issue reproduces on a clean project as well
• Reinstalling VSCode and the extension does not help
• Setting NODE_OPTIONS=--dns-result-order=ipv4first does not help
• Enabling long paths in Windows (LongPathsEnabled) does not help

[hgargova]

@yury-s could you take a look again, please

[Duy247]

This problem could be seen in any extension, you guys need to check if you guys are using company's PC or laptop, because your corporate machine may hide behind its own proxy.
Try adding it to VSCode via User Settings.
The fact that it appears after an OS update made me think of this

Edit: it could even be the global proxy setting of your PC, try fixing NO_PROXY env var to 127.0.0.1,localhost .

[IvanQL]

@Duy247 I tried but it was not solve a problem.

Btw the error is Illegal argument: character must be non-negative which is the Position constructor in the VS Code API. A Position requires (line, character) where both must be >= 0. The extension is passing a negative character index. I think in case of a proxy/network error in the stack would be http, net, socket, fetch, or request somewhere in the trace. There's none of that here. It's purely the extension failing to map an error location to a valid position in the editor

[lucsoft]

Does anyone here who is having this issue have an Antivirus installed (other then the default windows defender one)?

[framewerks]

We're seeing this same issue - have ESET AV and also AppLocker policies which may also be relevant?