From Fedora Project Wiki
Associated release criterion
This test case is associated with the Basic_Release_Criteria#updates release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Basic_Release_Criteria#updates release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#updates release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Fedora_42_Beta_Release_Criteria#updates release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Description
Ensure it's possible to install packages with a graphical package management tool
How to test
- Boot Fedora
- Log in
- Open GUI package manager (GNOME Software Center, etc)
- attempt to install a package (emacs, nginx, apache, etc)
- Use/configure the installed package
- reboot the instance
- verify installed package functions
Expected Results
The following must be true to consider this a successful test run.
- Package installation finishes without error
- The installed package runs without error
- System successfully reboots