Open dianabarsan opened 6 months ago
I have a PR open that adds the necessary changes to run e2e tests over k3d: https://github.com/medic/cht-core/pull/8978 The branch also adds the first two k3d based e2e integration test suites, but does not remove their corresponding docker based tests.
I'm proposing we merge the branch as-is and iterate over it over the course of the near future, deciding whether we remove the docker-compose based tests and so on.
Moved to 4.8.0 so as not to hold up the release.
I've added two e2e test suites that run tests over k3d. The suites are copies of the docker integration test suites.
I'm planning to let devs try them out, and once we've established stability, we can remove the docker suites and make the k3d suites required for merges.
Hi @dianabarsan have we established confident stability for the K3d e2e to close this or do I move this issue to 4.9.0 ?
Please move this to 4.9. We're still not running all e2e tests over k3d
Moved to 4.9.0 so as not to hold up the release.
Describe the issue We no longer support docker-compose deployments for production. Some bugs can potentially only be triggered by deploying CHT over k8s, for example: https://github.com/medic/cht-core/issues/8868
Describe the improvement you'd like Run at least one e2e test over a k8s deployed CHT. Ideally both supported architectures should be tested.
Describe alternatives you've considered Run all e2e tests over k8s.