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

Include deployment dependencies and readiness checks for registry operator integration test suite #1523

Open
2 tasks
michael-valdron opened this issue Apr 15, 2024 · 0 comments
Labels
area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues kind/user-story User story for new enhancement

Comments

@michael-valdron
Copy link
Member

michael-valdron commented Apr 15, 2024

/kind epic
/kind user-story

Which area this user story is related to?

/area registry

User Story

As a contributor to the registry operator, I want to have the ability to just use make test-integration whenever I want to run integration tests, so that I don't have to spend extra time on environment setup steps.

Currently, the integration test suite for the registry operator does not have a sufficient setup to ensure the registry operator deployment is ready before executing the integration test cases, as a result this leads consistent timeouts when trying to run make test-integration alone. To workaround this, one must do the following steps to ensure the target registry operator deployment is ready before integration test cases do:

  • Run make install-cert and wait for pods in cert-manager namespace.
  • Run make install && make deploy and wait for pods in registry-operator-system namespace.
  • Run make test-integration.

Doing the above will allow the integration test suite to run properly. It would be better though to include the first two steps as part of the setup process of the integration test suite so that you would only need to run make test-integration to execute everything.

Acceptance Criteria

@openshift-ci openshift-ci bot added kind/epic A high level requirement that can/should be split into smaller issues kind/user-story User story for new enhancement labels Apr 15, 2024
@michael-valdron michael-valdron added the area/registry Devfile registry for stacks and infrastructure label Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues kind/user-story User story for new enhancement
Projects
Status: Refinement
Development

No branches or pull requests

1 participant