Daniel

+1 for this. I ran into many situation where multiple locators are pretty much the same, except for their text. So it would be great to use the same locator...

> Found an even easier way, just drop this into your describe block or above your tests: `test.use({ storageState: { cookies: [], origins: [] } });` But this will still...

You can ignore all of the steps that come after `page.goto()`, because the same thing will happen even if I change to a one step test like opening Google and...

> @DanielStoica85 Unfortunately, I cannot reproduce the issue. `page.goto()` always works for me, but the test is stuck on `page.getByRole('link', { name: 'close' }).click()` because there is no "close" button...

I noticed something else that might be helpful. So like I said, navigation fails at first attempt, even when running the test by using the VS code extension. But after...

Thanks for getting back to me! All I see in the trace viewer (network tab) is this: As for your second suggestion, this is what I get: ``` pw:browser pid=29779...

If a network proxy/firewall would be the problem, then it would never work. But like I explained above, after failing for the first time, if you rerun (without closing the...

> same code that exhibited thisbehaviour, when moved to a different test with a different name (in same describe bracket) worked fine. > > so something is buggy in there....

> @DanielStoica85 could you please give us the output of `npx playwright --version`? > > Is your machine corp-hosted / managed by some company policies? Or do you have special...

Hey @mxschmitt ! Thanks a lot for still trying to help, I know it almost seems like a hopeless situation, but I am not ready to give up just yet,...