Getting e2e tests to run reliably locally

[ronaldlangeveld]

I have a pending PR, with a LGTM 🎉, however it's getting bottled necked by CI tests failing, preventing it to be merged.
I'm trying to reproduce it locally, but haven't been able to test reliably (even from main branch, with exact code with CI passing).
As I understand the instructions are, run dev environment locally in one terminal and then concurrently run e2e testing in another.

Tests run but there's always some failing.

I'm not sure if I'm missing a step in between or if they are just flaky?

Above is testing the latest commit which passes on CI but cannot get locally to pass. This is of course without my code added.

So I run npm run dev in one terminal and then npm run test-e2e-chromium in another.
I tried all the e2e variations, firefox, webkit.

I have no issues with unit tests.

System specs: Macbook M2 Pro, MacOS Ventura 13.4, Node v18.16.0.

Advice would be much appreciated!

[acywatson]

Weird - some of the tests are a bit flaky, but there shouldn't generally be any failing (might retry once) consistently locally.

Did you look at the output of the failures to see if there are any clues? I believe screen recordings should also be created in a local directory for failed tests. They might provide some insight as well.