Steps to test autopackage releases, starting from a clean slate:
Main functionality
- Install the 1.0 Foobar package, combinations:
- From the command line
- With "no password" when asked for the root password the first time
- With password the first time but not the second time
- Check that:
- It installs the foobar files correctly
- That it resolved the foobar-core dependency correctly
- That it installed the GTKFE correctly
- That it appears in the manager application
- Check that "package files foobar" works, "package verify foobar" works, "package uninstall foobar" works.
- Now do those checks again, and make sure they fail cleanly.
- Install it again. Now foobar should install but foobar-core shouldn't (as it's already there)
- Uninstall it using the graphical manager.
- Install it again, but inverting the user/root combination you used previously.
- Try uninstalling it as the "wrong" user, make sure it fails and/or you get prompted.
- Uninstall it using the graphical manager.
- Build a foobar RPM using checkinstall, install it, make sure it gets uninstalled when you install foobar
- Build an apbuild RPM that depends on foobar, install it, make sure that rpm foobar is not installed and we fail cleanly.
- Find a 1.2 C++ package
- Make sure you can launch it from the desktop environment
- Make sure the right C++ ABI is selected and installed.
- Make sure there are no visual glitches during uninstall.
Manager
Prerequisite: a couple of packages should be installed.
- Run "package list" in the terminal
- remember the list of packages
- Start the GTK+ manager
- It should show a filtered list of packages (only "desktop apps")
- Switch the filter to "All Applications"
- The list of packages should be the same as for "package list"
