Topic Test planning for F40

[Peter Boy]

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
[e-mail]

Timezone: CET (UTC+1) / CEST (UTC+2)

Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast

[Alexander Bokovoy]

On Срд, 31 сту 2024, Peter Boy wrote:
> 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)

FreeIPA tests in OpenQA cover criteria we have for Fedora Server.
We might want to run additional manual tests for upcoming integration
of FreeIPA/SSSD and GNOME 46 (see
https://fosdem.org/2024/schedule/event/fosdem-2024-2169-passwordless-authent...
this weekend). This would mean using Fedora Server's deployment of
FreeIPA and enrolling Fedora Workstation into that deployment, then
defining one of passwordless authentication methods for the user and
going through the new login experience in GNOME 46.

We are not there yet (the code is being written by both SSSD and GNOME
developers as we speak) but we will have something closer to Fedora 40
beta, I hope. Iker and Roy produce test packages in a COPR
ipedrosa/passwordles-gdm but that is not usable yet.

We also wanted to do interoperability tests between FreeIPA and Samba
AD. This is something we already should be able to do.
> 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?

AdamW would probably be the best person to give us guidance on it. For
FreeIPA there are already pages describing scenarios being tested by
OpenQA:
https://fedoraproject.org/wiki/Category:FreeIPA_Test_Cases
> 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
> [e-mail]
>
> Timezone: CET (UTC+1) / CEST (UTC+2)
>
> Fedora Server Edition Working Group member
> Fedora Docs team contributor and board member
> Java developer and enthusiast
>
> --
> _______________________________________________
> server mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue