[Bug]: Test run with parameter workers=0 (or a negative number) is treated as successful

[howlingtesters]

Version

1.58.2

Steps to reproduce

1. Create any tests.
2. Run tests with workers=0, for example:

• npx playwright test --workers=0

3. The tests do not run at all, but the process exits successfully.

Expected behavior

I would expect the same behavior as with forbidOnly - the entire test run should be marked as failed to prevent false positives in CI pipelines.

Actual behavior

The test run (even on CI pipeline) is marked as successful even though no tests are executed.

Additional context

Don’t ask me how this was discovered.
Hope to make your day better with this bug report - great one for the day before Prima Aprilis:)

Environment

System:
    OS: Windows 11 10.0.26200
    CPU: (20) x64 Intel(R) Core(TM) i5-14500HX
    Memory: 14.80 GB / 31.73 GB
  Binaries:
    Node: 25.0.0 - C:\nvm4w\nodejs\node.EXE
    npm: 11.6.2 - C:\nvm4w\nodejs\npm.CMD
  npmPackages:
    @playwright/test: ^1.58.2 => 1.58.2

[bwyard]

Looked into this. The validateProject in configLoader.ts catches workers: 0 for config files (number check at line 325), but CLI args bypass that path. --workers=0 goes directly to resolveWorkers(0), which parses to 0, passes the NaN check, and returns 0. Fix is a <= 0 check in resolveWorkers after the parseInt. This does not have the open to PR tag but cool to submit one if yall are open to it.