Skip to main content

Easily running a subset of playwright tests using tags

Feature RequestPlaywright

We have a large end to end testing repo that sits outside our main repository this has over 100 tests and takes 3 to 4 hours to run.

We already have tests marked with @smoke that we run on a more regular basis and would like to run a subset of these which we could tag with say @checkly to run them using your service.

I can set this up with new check files but it would be easier if the CLI supported the orginal tagging we have setup in playwright and also if it picked the test names.

It is a fairly standard way of running subsets of tests in QA tools.

Thanks for making a really cool tool!

Posted by chris-heathwood ·
Status: Completed6 comments

Log in to comment and vote

Comments6

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

    Sep 19, 2025

    Pinned

    Hey all! This is already available when using Playwright Check Suites, where you can pull a specific tag (or tags) using pwTags.

    You can also decide which playwright project it should use in combination (if none selected, it'll run across all projects/devices!)

    For example:

    ```typescript

    checks: {

    playwrightConfigPath: './playwright.config.ts',

    playwrightChecks: [

    {

    name: 'Critical suite in all device projects',

    logicalId:'critical-suite',

    pwTags: 'critical', // Reference a tag in your tests

    frequency: 5,

    locations:['us-west-1','eu-west-2','ap-northeast-1'],

    },

    ],

    }

    ```

    A full working example is available here. Let me know how you get on, and if you’ve got any questions!

  • María de Antón

    •

    Oct 24, 2025

    I just wanted to post a quick update now that Playwright Check Suites are generally available → 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!

    1

    Reply

  • Jonathan Canales

    •

    Nov 6, 2024

    Hi Chris!

    I’m sure you’ve already seen the CLI reference docs, but in case you haven’t you can absolutely use grepping and tags to run your spec files. You could also technically assign a tag to your check matching and the use the CLI to reference those tags as well.

    I’m curious about your use case, feel free to pop into the community slack and share more if you like.

    • --grep <pattern> or -g: Only run checks where the check name matches a regular expression.

    • --tags or -t: Filter the checks using a comma separated list of tags. Checks will only be run if they contain all the specified tags. Multiple --tags flags can be passed, in which case checks will be run if they match any of the --tags filters, i.e. --tags production,webapp --tags staging,backend will run checks with tags (production AND webapp) OR (staging AND backend).

    browserChecks: {

    frequency: 30,

    testMatch: ['./tests/e2e/login.spec.ts'],

    tags: ['browser'],

    },