As a developer, I want to have our e2e testing to work in a reasonable time when running the tests locally. Currently the e2e tests take over 30 seconds per successful test. Additionally the e2e test database is not used in every test as it should be, namely by the timetables-api and jore4-tiamat services.
The services currently get their connection parameters from environment variables that are read from the secrets, but for running e2e tests they should only get them from env vars. This should be changed if it already is not so.
Steps to fix:
[x] Split docker-compose generation to exdtendable base service, and normal service
[x] Configure timetables-api to accept environment overrides for database connection parameters
[x] Configure tiamat to accept environment overrides for database connection parameters
[x] Configure hasura to accept environment overrides for database connection parameters
[x] Set hasura to get tiamat graphql address from an environment variable
[x] Set the docker-compose.custom.yml in jore4-ui to start e2e-services using environmental variables for the database and service connections, so we do not need to have extra e2e versions of these images in Docker hub.
[ ] (Optional) Remove extra cy.visit function calls from e2e-tests. This should be only needed once per test, exceptions are tests that use the map. When running e2e-tests in local environment it uses dev build and it's not optimized and loads about 45MB each time cy.visit is called.
As a developer, I want to have our e2e testing to work in a reasonable time when running the tests locally. Currently the e2e tests take over 30 seconds per successful test. Additionally the e2e test database is not used in every test as it should be, namely by the timetables-api and jore4-tiamat services.
The services currently get their connection parameters from environment variables that are read from the secrets, but for running e2e tests they should only get them from env vars. This should be changed if it already is not so.
Steps to fix:
docker-compose.custom.ymlin jore4-ui to starte2e-services using environmental variables for the database and service connections, so we do not need to have extrae2eversions of these images in Docker hub.cy.visitfunction calls from e2e-tests. This should be only needed once per test, exceptions are tests that use the map. When running e2e-tests in local environment it uses dev build and it's not optimized and loads about 45MB each timecy.visitis called.