Dmitry Gozman

@dimkin-eu Conceptually, you can have a single server for all the tests, either external or started by playwright with `webServer` option, or have multiple servers where each test talks to...

@dimkin-eu I see, thank you for the information. Let me know whether the workaround above works for you. Meanwhile, we'll think about your usecase and similar ones, and any possible...

@dimkin-eu Yep, that's right. You can also re-export `expect` from the helper file, so that you write: ```ts import { test, expect } from './my-fixtures.ts'; ```

Also, [here is a guide](https://playwright.dev/docs/emulation#geolocation) for geolocation.

@harshith-aimyth Oh, sorry, I misunderstood. So you'd like not to `Allow`, but to `Block` with Playwright? This is not supported today. I'll leave this as a feature request.

@jameskip `--deny-permission-prompts` chromium flag works across all contexts, but Playwright will take that into account if you specify `launchOptions.args` for a single file: ```ts test.use({ launchOptions: { args: ['--deny-permission-prompts'] }...

I don't see any real different between the following two. If anything, the latter even gives me more control - for example, I can skip a test when `urlType` has...

@hungdao-testing Just make a few describes in a loop. ```js let arr = [1, 2, 3, 4, 5]; for (const tour of arr) { test.describe.only(`Looping ${tour}`, () => { test.beforeEach(async...

> I have the same problem as @alexkrolick Is there a way to avoid that? > > > Another limitation of `for ... of` is that if one test throws...

@Sunny1861 Electron is not a priority for Playwright, so I don't expect this to be fixed soon. Especially, without a clear repro script. > May I know what kind of...