Playwright

Run your Playwright suite against real browsers on macOS by connecting to the TestKase WebSocket endpoint. There are two ways to integrate, mirroring the SDK vs Direct split you may know from other vendors.

Two ways to connect

Recommended — the @testkase/playwright-reporter wrapper CLI

A drop-in for any existing Playwright project. Your test files and playwright.config.ts stay 100% native Playwright — no TestKase imports in your code.

1. Install the reporter:

   npm install --save-dev @testkase/playwright-reporter

2. Add a testkase.yml at your project root with credentials and capability flags:

   user:        you@example.com
   accessKey:   xyz_your_access_key
   browserName: Chrome
   recording:   true
   console:     true
   network:     true
   driver:      true

3. Run via the wrapper instead of npx playwright test:

   npx testkase-playwright test

With the wrapper, every capture kind lights up — recording, driver logs, browser console, network HAR, test names and pass/fail status, step labels, and per-test recording slicing — identically across Chrome, Edge, and Firefox.

Direct — the raw WebSocket endpoint

For locked-down CI or custom runners that can't run a wrapper, connect a vanilla @playwright/test install straight to the endpoint, with credentials and capability flags JSON-encoded in the query string:

wss://hub.testkase.com/playwright?capabilities=<url-encoded JSON>

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

const caps = encodeURIComponent(JSON.stringify({
  browserName: "Chrome",
  browserVersion: "latest",
  "testkase:options": {
    username: "you@company.com",
    accessKey: process.env.TESTKASE_ACCESS_KEY,
    build: "smoke-1",
    name: "checkout flow",
  },
}));

const browser = await chromium.connect(`wss://hub.testkase.com/playwright?capabilities=${caps}`);
const page = await (await browser.newContext()).newPage();
await page.goto("https://example.com");
await browser.close();

Feature coverage at a glance

On the Direct path you can still populate test names/status yourself by emitting testkase_action: magic strings from page.evaluate — the same pattern other vendors document.

Supported Playwright versions

TestKase keeps 5 Playwright versions installed concurrently. The Hub auto-detects your client version from the WebSocket handshake (or from testkase:options.playwrightVersion) and routes you to the matching in-VM library.

In-between clients (for example 1.57) resolve to the closest newer installed server (1.58). Clients below 1.50 or above 1.60 get a clear, actionable too-old / too-new error.

Firefox naming

Playwright ships a patched Firefox and exposes it as a separate brand, pw-firefox. You can simply write browserName: "Firefox" and the Hub aliases it transparently on the /playwright endpoint.

Next steps