Adam Banko

Here's an example page: https://app.tealcompass.com/results/4d3cd7c8-234a-4a22-87a8-51d651c83597 It's an app I'm working on, and the errors initially showed up on my local dev environment. I can only show it to you now...

Related: - https://github.com/microsoft/playwright/issues/22657

Possibly related error during code generation when importing an ESM module from a component. When running playwright component tests this ESM module imports and works fine. ``` Loading features from:...

Workaround: `const wrapper = createBddWrapper(test, (...args) => test(...args))` With createBddWrapper as ```ts type TestFn = ( ...args: Parameters ) => ReturnType export function createBddWrapper( test: T, callTest: TestFn, ) {...

Upgraded workaround also locates the describe blocks in the proper file ### Usage ```ts createBddWrapper(test, { describe: (...args) => test.describe(...args), test: (...args) => test(...args), }) ``` ### Definition ```ts import...

> If I got it wright, what you want is to make playwright understand that the features/scenarios have been defined in your .spec.ts file, regardless that they have actually been...

Hey @NikkTod , I had the same issue and found two workarounds: - the code above https://github.com/Niitch/gherkin-wrapper/issues/4#issuecomment-1546982920 - use `--grep` on the name of the describe / test instead of...

+1

Thanks for reporting! I just bumped into the same issue while playwright testing using concurrent workers. I'm happy to provide more details if it helps to debug and fix this...

Hi, the workarounds I found was adding retries to our playwright tests or using the built version of our app to run the tests instead of the dev server