I’m working at a company that continuously deploys various microservices to kubernetes throughout the day and I’m trying to work out where best to slot in some UI E2E tests.
As part of any successful PR we first deploy to a staging environment, then if that succeeds it automatically goes out to production. Unit and integration tests are performed before deploying to staging.
Because of the complexity and size of the system, it’s not possible to spin up a kubernetes cluster and run the system as a whole.
Some UI tests could be run after deploying to staging but every pipeline would have to be updated (We have over 100) to accomodate these tests. It’s also possible the teams won’t be happy with the extra time that is adding to the build and deploy process.
Or you could have a seperate pipeline that just runs UI tests periodically. You wouldn’t get that fast feedback about what specific change might’ve caused an issue but you also wouldn’t get that potential interference that UI tests can potentially bring.
Any thoughts on this?