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]: Use e2e tests based on the catalog level #40

Closed
Tracked by #113
whg517 opened this issue Apr 17, 2024 · 0 comments
Closed
Tracked by #113

[Enhancement]: Use e2e tests based on the catalog level #40

whg517 opened this issue Apr 17, 2024 · 0 comments

Comments

@whg517
Copy link
Member

whg517 commented Apr 17, 2024

The current test simply deploys the operator resource manifest to the test cluster using make deploy and checks that the results meet expectations. In actual production, however, the operator is installed through OLM based on the catalog schema, and the service is deployed through the operator.

Test cases cannot be overwritten to the olm management operator phase. The operator may not be found in the catalog, or the subscription installed in operator-group may fail to be installed due to incorrect installation mode, permission configuration, and other problems. This is a disastrous problem for non-K8S experts. To avoid the unpredictability of the full life cycle, we should add testing of the catalog deployment pattern to the e2e process. Or simply replace it with tests based on the catalog deployment pattern.

@tutunannan tutunannan changed the title [enhance]Use e2e tests based on the catalog level [Enhancement]: Use e2e tests based on the catalog level May 22, 2024
@whg517 whg517 closed this as completed Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant