| Anaconda WebUI for Fedora Workstation by default | |
|---|---|
| |
| Date | 2024-11-11 to 2024-11-18 |
| Time | all day |
| Website | QA/Test Days |
| Matrix | #workstation:fedoraproject.org |
| Mailing list | test |
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.
What to test?
This Test Day will focus on testing case and giving feedback on Anaconda WebUI by Default for Fedora Workstation. This changeset was pushed to next Fedora release and these test days will help determine how the experience is shaping up to be!
Who's available?
The following cast of characters will be available for testing, workarounds, bug fixes, and general discussion:
- Development - Jiří Konečný (jkonecny) et anaconda team
- Quality Assurance - Sumantro Mukherjee (sumantrom), Geoffrey Marr (coremodule), Kamil Paral (kparal), Adam Williamson (adamw)
You can chat with us on Matrix or IRC. See the infobox on top of the page to learn where to join.
Prerequisites for Test Day
- Fedora Rawhide nightly ISO image installed on either bare metal or in a virtual machine. (Make sure you have no important data on that system. Things might go wrong -- don't do this on your production machine!)
- Please use the latest ISO whenever you are attempting to test
How to test?
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.
Reporting bugs
Please file bugs inRed Hat Bugzilla under . Each application has its own separate project, just search for it.
Please note that just mentioning your problem into the comments section on the results page is not very helpful. Very often those problems only happen in specific circumstances, or with specific steps taken. We need the logs and screenshots, and we need to be able to ask you followup questions. Please file bug reports, it's much more useful than a short comment. Thank you!
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!