What to test?
Today's installment of Fedora Test Day will focus on testing
- feedback on modularity
- serious regressions to YUM v3
- user experience issues (inconsistencies, awkward behavior)
- any performance issues
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion. In case of problem related to test day organization/wiki/whatever, please reach out to sumantrom.
- Development - dmach (dmach)
- Quality Assurance - Adam Williamson (adamw),coremodule (coremodule), Sumantro Mukherjee (sumantrom)
Prerequisite for Test Day
- A system (real or virtual) you can install Fedora to, and not mind if it breaks
- A Fedora 29 image: download beta Workstation or Server, or a Fedora 29 nightly image
How to test?
Install Fedora 29
Testing DNF from a live environment is difficult and will likely wind up with the system exhausting available RAM and failing in strange ways, so we recommend you install Fedora 29 for this Test Day.
Update your machine
Make sure you have all the current updates installed, using the update manager. Note that a clean installed Fedora 29 system will have DNF 3.5.1, while after update from updates-testing (which is enabled by default), you should have DNF 3.6.1 from this update. We are interested in tests with both versions. If you find an issue with one version, it would be very useful to check if it also happens with the other.
Run the tests
Visit the result page and click on the column title links to see the tests that need to be run: most column titles are links to a specific test case. Follow the instructions there, then enter your results by clicking the Enter result button for the test.
If you have problems with any of the tests, report a bug to Bugzilla usually for the component dnf. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you.
Please enter your results on the result page. The results will be transferred here after the Test Day is finished.