Test Case in place : https://fedoraproject.org/wiki/QA:Testcase_DNF_5_system-upgrade

Known Regression/Issue: DNF 5.2 is not available in Fedora 38, 39, or 40 (it is ABI-incompatible with DNF 5.1), so testers will probably need to get the latest version of DNF 5 from our COPR: https://copr.fedorainfracloud.org/coprs/rpmsoftwaremanagement/dnf5-unstable/.

wiki : https://fedoraproject.org/w/index.php?title=Test_Day:2024-06-05_Fedora_41_DNF_5.2
test event : https://testdays.fedoraproject.org/events/189

@jkolarik, I've updated the system-upgrade test case and created the event. We will be testing everything more or less but stressing on system-upgrade feature as it makes it's first appreance in DNF5.2. Please review and lemme know. :)

I've briefly reviewed the mentioned test cases, which are probably retaken from dnf4. Here are some modifications according to the changes introduced in dnf5 (see docs here):

• config-manager
  • Syntax has changed (see docs here)
  • To enable a repo: dnf5 config-manager setopt repoid.enabled=1
  • To disable a repo: dnf5 config-manager setopt repoid.enabled=0
  • No more dnf5 enable or dnf5 disable shortcuts
• history
  • No default dnf5 history command; a specific subcommand is needed, e.g., dnf5 history info
  • The mentioned test case is relevant only if a package was previously installed using dnf5

Also, I noticed that sometimes dnf is mentioned, and sometimes dnf5. This distinction is important if users use the dnf5-unstable repo, where dnf refers to dnf4 and dnf5 is a separate command. Otherwise, it seems fine.