E2E testing: specific Docker image
plumdog opened this issue · 0 comments
plumdog commented
To allow my "monster" to rest in peace (see #78), should replace it with a "e2e-testing" image that is produced alongside the tagged releases. So, for eg, version for 1.2.3 there would also be a 1.2.3 e2e-testing image. (This could live in the same Docker Hub repository, or in a separate one, I don't think it matters.)
Ideally it would:
- have both firefox and chrome installed (see #87)
- have the real (non-bundled) frontend codebase and dependencies and node/npm versions, sufficient to run the tests
- allow easy configuration of the things the horrible code in #78 does with
sed:- setting concurrency
- setting which browser to use (firefox and/or chrome)
- turn off the
video*options (I tried turning these off, because I suspect they meant more CPU was getting used, which is in short supply, but this is just a hunch. But certainly, we never retrieve the videos anyway.) - an easier and more reliable way of setting the name for the
E2E_TEST_TOKEN_[environment]env var. I got a bit confused about what was going on here, tbh.