Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement] Run cluster based integration tests as e2e tests & enable them in prow using emulators #722

Open
anveshreddy18 opened this issue Apr 1, 2024 · 0 comments · May be fixed by #743
Assignees
Labels
kind/enhancement Enhancement, improvement, extension

Comments

@anveshreddy18
Copy link
Contributor

anveshreddy18 commented Apr 1, 2024

Enhancement (What you would like to be added):

Currently the integration tests and integrationcluster tests of etcdbr are under test/e2e folder. This issue aims to enable these e2e tests to be run as prow job upon whenever a PR is raised like in etcd-druid. Configure the prow job to be run with storage emulators like localstack, fake-gcs-server & Azurite instead of real infra. And also move the integration tests to under test/ to standardise the directory structure.

The tests can also be configured to run with real infra, this way developers can be sure about their changes especially to the storage SDKs and APIs.

Motivation (Why is this needed?):

By having e2e tests separately, it can be run as a standalone test in prow job with multiple cloud storage emulators running in parallel, as this will ensure any changes made to the codebase are properly tested with different cloud providers before pushing them.

Approach/Hint to the implement solution (optional):

@anveshreddy18 anveshreddy18 added the kind/enhancement Enhancement, improvement, extension label Apr 1, 2024
@anveshreddy18 anveshreddy18 self-assigned this Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension
Projects
None yet
1 participant