Pavel Feldman

Closing as per above as non-actionable, but open to a PR from the reporter!

They are all available under the Before Hooks. Here is how fixtures work: ```js allureFixture: async ({}, use) => { // this code runs before test for setup await use();...

Closing as per above

We no longer have multiple vscode projects, we manage it using our own UI now. Closing as addressed please file an issue once we ship the new version of the...

It is a Playwright Test bug.

Allowing the following code was an oversight on our side. Mixing the test instances (and hooks called on those instances) in the same suite prevents us from keeping the strict...

I updated the release notes to include this as a breaking change. Is there a reason you need to mix test instances? Can you fix the code?

> I'm aware the alternative to this is to either compile our project beforehand and run playwright on dist, or to run next.js in a separate process and make sure...

Could you help me understand why we need to register component in beforeMount for this use case to work? I was hoping it would work out of the box.

Ah, I missed the string quotes around \, it makes sense to me now. In terms of the proposed shape of the API, I see hooksConfig as a user object...