← All changelogs

Changelog

Playwright Check Suites: cancel runs, choose node/bun versions and more

Published

Cancel runs whenever you need to

Playwright Check Suite runs are now cancellable. You can stop queued or in-progress runs from the Playwright Check Suite Runs or Test Session Run pages, or press CTRL+C on Checkly CLI 8.0.0 and later. This works for runs started from Schedule now and for test sessions triggered via npx checkly test, npx checkly pw-test, and npx checkly trigger; cancelled runs show a Cancelled status in your run history.

Choose your Node/Bun runtime engine

Playwright Check Suites now support multiple Node.js and Bun engines, configurable from the UI or in code. Starting with Checkly CLI 8.1.0, the CLI reads your project's version files (.nvmrc, .node-version, .bun-version) and selects a compatible runtime automatically, with Node.js 22 (default), 24, and 26 and Bun 1.3 supported. You can override detection by setting the engine property on your PlaywrightCheck, for example engine: Engine.node('24').

Browser caching across runs in Private Locations

Check Suites now cache Playwright browsers across runs on the same Private Location agent, so the installation step is skipped entirely when a cached version exists. That means faster startup, no repeated downloads, and lower bandwidth usage, with zero configuration required. Caching is scoped per agent and available since Private Location agent version 8.2.0.

Private Location agent changelog →

Also shipped

  • globalTimeout: Playwright's globalTimeout is now fully supported: set it in playwright.config.ts or via --global-timeout in your testCommand, and timeout errors now appear in logs and the Failures tab.
  • Setup retries: Environment setup steps prone to transient failures (pnpm install, Corepack, dependency cache downloads) now retry automatically with backoff, no configuration needed.
  • Dependency cache: The dependencies cache moved to a Least Recently Used cache, so all Playwright Check Suites now reuse and automatically refresh the same cache key instead of letting it expire.
  • Trace logs: Check logs now surface post-processing details, including report generation, trace processing, and trace sanitizing, each with its own timing.