Using the @testkase CLI

There are two ways to reach our browsers with Playwright. Writing the connect address yourself is one — see First test in JavaScript.

This is the other: a wrapper that runs your tests as-is. Your test files and your playwright.config.ts stay exactly as they are, and one new file says where to run them.

It is the better choice if you already have a set of tests. It also reports test names and results for you, which you would otherwise write by hand.

1. Install it

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

2. Add a testkase.yml

In your project root:

accessKey:    xyz_your_access_key_here
browserName:  Chrome
platformName: Windows 11

# Optional
name:         checkout suite
build:        ci-${CI_BUILD_ID}
browserVersion: latest
tags:         [smoke, checkout]

# All four are OFF unless you turn them on
recording: true
console:   true
network:   true
driver:    true

3. Run it

npx testkase-playwright test

Every argument after test is passed straight to Playwright, so --project, --grep, --workers and the rest all behave normally.

What it does that you would otherwise do yourself

It names your tests. Each test's own title becomes the test name on the session, and its result becomes the outcome. Nothing to add to your specs — this is the whole of Marking tests, done for you.

It groups the run. The wrapper makes a fresh run id each time you run it and hands it to every worker, so one command is one run in your dashboard however many workers it used. That is why there is no runId key in the file above — setting one would only fight it.

It sizes the page to the window. We size the remote browser to resolution; the wrapper then lets the page fill that window. Set your own viewport in testkase.yml or in playwright.config.ts if you need a fixed page size — anything you set yourself wins.

Which to use