I believe the purpose of the test case is to have a very generic test case that works in all environments (not just graphical ones) and applies to all package managers (notably dnf, packagekit, gnome-software, discover, dnfdragora, etc -- but not rpm, that is one level below them). It relies on rpm working correctly in the bottom, and it doesn't care about the actual software that gets installed. The point is just to ensure the selected package got installed or removed (which can be easily verified with rpm). Checking app icons in the desktop menus or launching them is a departure from this goal. And it doesn't work e.g. in Server environment. Also, I try to avoid hardcoding package names like you did (install packages foo and bar), because it's the random nature of things that helps up detect issues during manual testing. We can hint the package names, if really needed. I'm not saying the changes are wrong, it just seems to be a different test case. Something that would perhaps fit more into desktop testing and be tied to graphical package managers, than to be a completely general test case.
I believe I have improved the generalization and retained the application test.
The updated version is at: https://fedoraproject.org/wiki/User:Tablepc/Draft_Testcase_package_install_remove Have a Great Day! Pat (tablepc) _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/test@xxxxxxxxxxxxxxxxxxxxxxx
