With Cypress, you can easily create tests for your modern web applications, debug them visually, and automatically run them in your continuous integration builds.

Cypress Community

In the same computer, CI always fails, while normal e2e works.

The case is a select where it should click, then type, then choose the option, it works while normal, why doesn't it work in the CI mode?

Could you provide more details? What commands you are using for “normal e2e” vs “CI mode”? Is it possible to share the test code itself, or even better the whole project?

Sure, my project is a quasar, but under the hood, is vite with vue 3, so in normal e2e, its compiling in run time, which should, make it less reliable, but it doesn't.

While, in the CI mode, its a compiled minimified version.

The commands 
```    "test:e2e": "cross-env NODE_ENV=test start-test \"quasar dev\" http-get://localhost:9000 \"cypress open --e2e\"",
    "test:e2e:ci": "cross-env NODE_ENV=test CYPRESS_API_URL=$API_URL start-test \"servor dist/spa index.html 9000 --silent\" http-get://localhost:9000 \"cypress run --e2e --browser firefox\"",
```

It seems something about animations? I'm not sure, but the videos doesnt show animations on the fields which most of the fails happens.