-
Notifications
You must be signed in to change notification settings - Fork 48
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
Review tests in microdnf directory #1579
Conversation
Is it really worth it to keep the microdnf tests in the separate microdnf directory if it's just an alias for the dnf5 command? In past, we had run tests explicitly with "dnf", "dnf-3" and "yum", maybe it was even possible to switch the command for all the tests, I am not sure exactly. But having the test at one place and only switching the command name seems better than to have a somewhat duplicate sets of tests. I can imagine it might be a lot of work to change it, but it would be more maintainable later. |
Most of them are duplicate to install-xml-base.feature
They are mostly present in reinstall.feature and reinstall-reason.feature
Also drops one duplicate basic config tests
Also removes one duplicate tag in original.
Also updates the existing makecache test and annotates it.
They have basically the same functinality as the current dnf module-reset but they are more structured and use appropriate steps.
One duplicate test is removed and the feature is specialized to multiline config.
Also one test moved to dnf and one dnf test updated
I have update the PR to de-duplicate and merge the |
A lot of the tests are duplicate to regular dnf5 tests but they are run through the
microdnf
command.