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

[epic] Implement upgrade tests for OperatorController #856

Open
joelanford opened this issue May 15, 2024 · 3 comments · May be fixed by #1003
Open

[epic] Implement upgrade tests for OperatorController #856

joelanford opened this issue May 15, 2024 · 3 comments · May be fixed by #1003
Assignees
Labels
epic v1.0 Issues related to the initial stable release of OLMv1

Comments

@joelanford
Copy link
Member

joelanford commented May 15, 2024

In order to have confidence that feature additions and bug fixes are reflected after an upgrade, we should add a suite of upgrade tests that:

  1. Install the most recent public release.
  2. Create objects that sufficiently exercise our API surface and behaviors.
  3. Upgrade in place from the most recent public release to a build from the current commit.
  4. Make assertions that prove that changes from the current commit are reflected.
@joelanford joelanford added epic v1.0 Issues related to the initial stable release of OLMv1 labels May 15, 2024
@acmenezes
Copy link
Contributor

/assign

@acmenezes
Copy link
Contributor

Hi @joelanford , I'm sorry I didn't have much progress on this task on the previous week. I'm quite busy with some partner work here. I'll just drop an /unassign here to open space for others to work on this. As soon as I have a few extra cycles I'll be back.

@acmenezes
Copy link
Contributor

/unassign

@m1kola m1kola linked a pull request Jul 3, 2024 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic v1.0 Issues related to the initial stable release of OLMv1
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants