Release 1.1.5 — Playwright snippet names platform, not os

[jochen-testingbot]

The bug

setupTestingBot's Playwright config snippet (src/tools/project.ts:398) emitted os: 'WIN11' into the wss://cloud.testingbot.com/playwright query string.

The hub never reads os. Utils.generateCapabilities in ws-hub (src/utils.ts:93-96) sets the session platform from platform or platformName and nothing else:

if (params.platform) {
    capabilities.platform = params.platform.toString()
} else if (params.platformName) {
    capabilities.platform = params.platformName.toString()
}

os still lands in desiredCapabilities via the catch-all loop at src/utils.ts:48-50, so it gets forwarded downstream as a stray key — but Capabilities.platform stays undefined and toDesiredCaps() (src/models/capabilities.ts:60) omits platform from the payload. Result: anyone pasting the snippet silently ran on the default platform instead of Windows 11, with no error to hint at it.

src/tools/cdp.ts:19 and the selenium/wdio snippets in the same file already use platform/platformName. The Playwright snippet was the only outlier.

The fix

One line: os: 'WIN11' → platform: 'WIN11'.

Test

Added a regression test asserting the snippet contains platform: 'WIN11' and not os: 'WIN11'. Verified it fails against the old line and passes against the fix. Full suite: 255 passed (19 files); lint, format:check and tsc clean.

Not changed

The flat query-param form is correct here and is not a limitation:

• name and build are read flat by the hub (utils.ts:84, :88).
• Putting tb:options in a query string would actually break — the handler at utils.ts:179 does for (const option in tbOptions), and a query param arrives as a string, so it would iterate character indices. The richer form over WS is ?capabilities=<urlencoded JSON>, which parseQueryParams JSON-parses and spreads flat.
• realDevice does not exist in ws-hub at all; it's a Selenium-hub concept.

Release

Version bumped to 1.1.5; manifest.json and server.json synced via npm run version:sync.