|Anaconda Web UI|
|Date||2023-08-28 to 2023-09-04|
What to test?
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:
- Development - Vojtěch Trefný (vtrefny), Martin Kolman (mkolman)
- Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)
Prerequisite for Test Day
- A virtual machine or a bare metal machine
- An installation of Fedora 39 Workstation. Make sure to fully update your system. If installing a fresh system, it's recommended to use the latest nightly image.
How to test?
The new web UI is not just a change of the UI technology, which is based on the React and Cockpit framework, but also a complete overhaul of the user experience. The new UI is trying to be easier to use by removing most of the complexities but still leaving possibilities to do everything you might need to do. We are trying to achieve a state where even users who don’t have previous experience with the Linux operating system will be able to do the installation smoothly.
List of what is part of the new UI:
- Wizard solution instead of hub and spoke
- New welcome screen to select language (will be preselected from a language configured in system)
- Timezone and date configuration
- Disk selection
- Guided partitioning
- Review configuration
- Installation progress
- Build-in help
Visit the results 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.
Please also try to experiment and explore and perform tasks not mentioned in any of the pre-defined test cases.
Perhaps you've found an already-reported bug. Please look at:
New bugs should be filed into Red Hat Bugzilla, in most cases against the
When filing the bug, it's very helpful to include:
- exact steps you've performed (and whether you can reproduce it again)
- screenshots or videos, if applicable
- system journal (log), which you can retrieve by
journalctl -b > journal.txt
- all output in a terminal, if started from a terminal
- your system description
If you are unsure about exactly how to file the report or what other information to include, just ask us.
Please make sure to link to the bug when submitting your test result, thanks!
Test results will be exported here once the test day is over. See How to test? section for information how to submit results and see the live results.