See issue https://pagure.io/fedora-server/issue/125
We should discuss and organize 2 topics, I think
a) What do we want to manually test? ====================================
At the very least, we should conduct a "smoke test" of the installation media and also of the most important functions. - Does it work as expected - any irregulary warnings or error messages? - Any SELinux issues? - Correct screen display (no distortions)? - Follow the corresponding documentation, if exists, what updates are needed (create ticket for each doc)
Items requiring testing - full default installation x86 - full RAID installation x86 - network default installation x86 - Create aarch64 SBC runtime image - Update an existing installation using dnf upgrade plugin (x86) - Update an existing aarch64 SBC - Adding virtualization - Instantiate a Fedora Server VM - Install systemd-container infrastructure - Create a systemd system container - Installing httpd and create a custom website - Install PostgreSQL and create a test database - Update an existing database - Manual tests of IPA (don’t remember the details, @abbra @sgallagh)
Either we should use the general QA WIKI page for Server tests or we may create a specific Server WIKI page for test results? In the former case we should create a short description for each test to use in the test table.
Maybe we should create a short guide how to use the QA test page for server?
b) What are the potentially critical changes that we should specifically monitor and test?
The list of Change proposals should b e complete now. Someone has to check these.
-- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy@fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast