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

e2e: tests should not rely on ocm-ramen-samples #1681

Open
Tracked by #1717
raghavendra-talur opened this issue Nov 26, 2024 · 0 comments
Open
Tracked by #1717

e2e: tests should not rely on ocm-ramen-samples #1681

raghavendra-talur opened this issue Nov 26, 2024 · 0 comments
Labels
enhancement New feature or request test Testing related issue

Comments

@raghavendra-talur
Copy link
Member

raghavendra-talur commented Nov 26, 2024

It would be really useful to have a set of e2e tests where the workload is defined and generated within the e2e code and used on the fly.

What we would need is a git repo to host the temporary artifacts. I think it should be easy to host a git service in the hub cluster and then use it for ACM/OCM.

Another way may be to use s3 store as the backend instead of git. We already have minio on drenv and whatever s3 solution openshift is using. We just need to push the resources there and configure the channel, subscription, and applicationset to use it.

This will allow us to create workloads with many flavors(pvc types, numbers).

Links:

See also #1459

@nirs nirs added enhancement New feature or request test Testing related issue labels Nov 26, 2024
@nirs nirs changed the title e2e tests should not rely on ocm-ramen-samples e2e: tests should not rely on ocm-ramen-samples Dec 5, 2024
This was referenced Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request test Testing related issue
Projects
None yet
Development

No branches or pull requests

2 participants