I reckon that what you want to do is to run tests that are generated using playwright codegen with Jest.

However, this does not seem to be possible: The tests are generated with import { test, expect } from '@playwright/test' at the top, and this is the module that throws the error. The tests that are generated with Playwright use the API from this module, and this is slightly different than the one from Jest. (It gets fixtures as parameters).

If you use the implementation from Playwright (for instance by mocking away the throwIfRunningInsideJest function), it still won't work because then the tests won't be registered in the Jest test runner.

Okay, so I found out a regex solution to my problem. It still seems a little less than ideal, but this is better than to add skip() in my opinion.

Apparently jest makes this pretty easy with just an extra argument to be added with the run command. This argument is treated as a regular expression to match against the Test Suite files in the folder structure.

Providing a pattern as a cli argument, is a way for it to pick only the files matching that regex and executing them -

jest "my.*(complex)?pattern"

I had to define a pattern to exclude a string in the file name. Since I wanted to exclude a file with "BVT" text in the file name, adding this to the package.json scripts, worked in my case -

"excludeBVT": "jest \"^((?!BVT).)*$\" -c jest.config.js"

You can use grep or grepInvert to skip over certain tests in projects. So something like this might work:

{
  name: 'Admin Users',
  grep:  /.*limited.spec.ts/,
  grepInvert: /.*comments.spec.ts/
  use: {
    baseURL: process.env.URL,
    screenshot: "only-on-failure",
    video: "retain-on-failure",
    storageState: 'login2.json', 
    headless: true,
    channel: 'chrome',
    viewport: { width: 1536, height: 850 },
    ignoreHTTPSErrors: true,
  }     
},

Maybe you need to adapt the regex to match your needs.