Skip to main content

Global playwright.config.ts support (viewport, setup, teardown, storageState ...)

To truly unite E2E testing and monitoring, Checkly CLI has to support the global configuration defined in playwright.config.ts, so that it can be used in both scenarios.

playwright.config.ts is very useful to handle stuff like:

  • Common viewport for tests

  • Common setup, teardown for tests

  • Common storageState for tests

  • Turn screenshot, trace, video on/off

  • And all the other useful playwright.config features that make playwright awesome

Status: Completed14 comments

Log in to comment and vote

Comments14

  • María de Antón changed status to Completed
    •

    Oct 24, 2025

    Pinned

    This is exactly and absolutely available with Playwright Check Suites! Thank you all for requesting and upvoting this feature in the first place!

    There’s now full playwright.config.ts (or .js) support and here’s how to get started.

    No wrappers. No rewrites. Just run your existing Playwright tests as scheduled checks. Support includes:

    • Projects (great for browser, env, and auth separation)

    • Multi-browser (Chromium, Firefox, WebKit)

    • Mobile device emulations (hi you, iphone-12, we’ve seen you often during the beta phase!)

    • Private/public npm dependencies

    • Feature-rich tests with setup hooks, fake devices, media access, and network mocking

    • Use a custom testCommand to make each Check suite, completely yours.


    On top of this, you also get full playwright compatibility: Projects, multiple-browsers, fake media devices, custom dependencies, you name it.


    If you have any questions, please, do ask! As the PM behind these new checks, I’m here for it!

    Happy monitoring!

  • Shashank

    •

    Jul 13, 2023

    Its also important to implement retries which are not supported when the checks are initiated as part of Vercel deployments.

  • Tim Nolet

    •

    Jan 26, 2024

    Hi all, we just released a first beta of this feature. This beta supports a whole range of global properties already, but not all. We will work on the remaining features + a cool way store your storageState credentials across check runs before we go GA but we did not want to wait.

    We also just removed 146 lines of code from our code base (that uses Playwright and the Checkly CLI) by already adopting this.

    Check out the full changelog here.

  • Thareek Anvar M

    •

    Dec 22, 2023

    This is an important one . because for my webapp test all test need authentication .so i need auth skip support .its nicely done from playwrite side .so if u guys support this would be very nice . we are using auth.setup.ts " its not supporting by checkly"

  • María de Antón

    •

    Apr 7, 2025

    Hi everyone, we have an alpha that supports all of playwright.config features along with custom dependencies — please let me know here or in Slack, and I’ll get you in!

  • Melissa Artison

    •

    May 8, 2025

    Prev fill in

  • dwane.debono@find.co

    •

    Oct 26, 2025

    I’m still seeing issues with unsupported dependencies:

    ❯ npx checkly pw-test -- --project Checkly Parsing your Playwright project... ✅

    Validating project resources... ✅

    Bundling project resources... ❌

    Error: Unsupported file extension for /Users/myuser/IdeaProjects/test-project/e2e-tests/node_modules/@faker-js/faker/dist/index.cjs
    
  • Tim Nolet

    •

    Jun 30, 2023

    We are closely looking at supporting this soon. More upvotes are always welcome of course!

  • Tim Nolet

    •

    Jul 13, 2023

    Hi, please ask questions or ask for general support in our Slack community https://www.checklyhq.com/slack/ or hit the chat bubble in the app. We're happy to help, but this portal is for feature requests only.

  • Tim Nolet

    •

    Jul 28, 2023

    Hi, we have a draft RFC up for this on CLI repo as we are looking at how to support the full playwright.config.ts file. Feel free to comment on or follow that one too.

    https://github.com/checkly/checkly-cli/issues/806