Curtis Conard

There is a hook for Cypress that lets you run code before any spec files are run. https://docs.cypress.io/api/plugins/before-run-api It might be possible to make a request to the bootstrap file...

> It's better but I still have some issues with virtual dom > Capture.video.du.07-03-2024.15.46.16.webm I'm not seeing that issue and I'm not sure why the rendering would be so slow...

> Or we could also consider that our e2e test suite should be resilient and we could make tests that will always pass, even when some data has already been...

So close to finishing this, yet dashboard JS errors are the only thing still blocking me. If anyone has suggestions, I'd be happy to take them. Clearly intercepting the AJAX...

> After a checkout right now: ![image](https://private-user-images.githubusercontent.com/418844/317752032- > Tried to logout/login, same. I can only recreate if I don't do a `composer build` after checking out the branch and prevent...

🎊 Finally all tests pass. E2E tests now work regardless of which order the test suites run in. If you run e2e locally and then try running unit or functional...

> I've tried to run tests locally. I've installed a fresh DB test instance (`--config-dir=./tests/config`), launched from PHP internal server with `php -S localhost:8088 tests/router.php`, ad adapted `tests/cypress.config.js`. Tests begin...

> Maybe we could have some `.env` config file to be able to run the tests without docker if needed ? This would allow to configure `CYPRESS_BASE_URL`, `CYPRESS_LOGIN` and `CYPRESS_PASSWORD`...

It isn't just you; I see the same issues. It clearly isn't happy with the built-in PHP server.

There is much more that is needed for this client request, but I think this PR is still relevant and able to be reviewed/merged on its own.