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

Testing dnf4 bootc #563

Open
evan-goode opened this issue Oct 18, 2024 · 2 comments
Open

Testing dnf4 bootc #563

evan-goode opened this issue Oct 18, 2024 · 2 comments

Comments

@evan-goode
Copy link
Member

The DNF 4 bootc plugin needs integration tests, and ci-dnf-stack is not equipped to test things meant for OSTree systems. Some unanswered questions are:

  • Where should test source code live? IMO, as much as possible should be in this upstream repository.
  • What testing framework should we use?
  • Where should the tests run (GHA, CoreOS Jenkins, Testing Farm)?
  • Should we write the tests from scratch, or base them on existing rpm-ostree and/or bootc tests?
  • Will any of the answers to the above need to change as development of the bootc plugin progresses?
@evan-goode
Copy link
Member Author

cc @cgwalters

@cgwalters
Copy link

Where should the tests run (GHA, CoreOS Jenkins, Testing Farm)?

I think Testing Farm is likely the most practical. (Which also points to the "testing framework" issue, we've tried to make tmt work)

Should we write the tests from scratch, or base them on existing rpm-ostree and/or bootc tests?

There may be some bits that could be copied, but I'm not sure how much. Probably the most interesting thing here is that at least on the bootc side we build a container with the updated bootc and test that.


In the more medium term I think we may try to reprioritize "run bootc/ostree in a container" which would dramatically simplify this story.

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

2 participants