QA/TestResults/Fedora9PackageKit/Rawhide

From FedoraProject

Jump to: navigation, search

Contents

Test Summary - QA/TestResults/Fedora9PackageKit/Rawhide

Known Bugs

  • Bug 441062 - reported by BayardCoolidge
  • A ton of SELinux avc denials -- expecting to search bugzilla shortly
  • When using gpk-application, two versions of a package are show.
yum repo1 contains package-1.1
yum repo2 contains package-1.2

Clicking on and installing the repo1 package, results in repo2 being installed (as it's newer). This makes sense, but isn't clear when walking through the UI.

tier#1

Idea.png
Feeling adventurous? All of the following test cases need to be defined.
Test Case Environment(s) Tested By Notes
QA/TestCases/PackageKitPkApplicationList Test listing RPMs using the gpk-application program. x86_64 JamesLaska Searched for several desktop apps. A already installed package (with update available) appeared to not be installed using gpk-application
QA/TestCases/PackageKitPkApplicationInstall Test installing RPMs using the gpk-application program. x86_64 JamesLaska Installed nautilus-open-terminal from gpk-application
QA/TestCases/PackageKitPkApplicationUpdate Test updating RPMs using the gpk-application program. x86_64 JamesLaska Added a local repo which included a updated package. Installed via gpk-application
QA/TestCases/PackageKitNotifcation Test notification of updates by the gpk-update-icon application, depending upon options set using the pk-prefs app. x86_64 JamesLaska Added a local repo which contained a newer package
QA/TestCases/PackageKitUpdateViewer Test package updates using the gpk-update-viewer application x86_64 JamesLaska Good in general, but there seem to be some odd timing issues. The icon will indicate a new package available, running code gpk-update-viewer/code manually shows no updates available.
QA/TestCases/PackageKitUpdateFrequency Verify that options for update frequency behave as intended. i386 MatthiasClasen The latest update made the "never" option work. The documentation needs some hints that the frequencies are only approximate and other events may trigger updates. This has been added upstream and will be in the next update
QA/TestCases/PackageKitAutoInstall Verify that options for automatic installation behave as intended. all
QA/TestCases/PackageKitSecurityUpdateIcon Verify that security updates get the right icon. Note: the dummy backend for !PackageKit provides such metadata, rawhide does not i386 MatthiasClasen Tested with the dummy backend. Works as expected, security updates get a bright red star
QA/TestCases/PackageKitUpdateMeta Verify that update metadata (e.g xrefs to bugs and CVEs) are displayed correctly and functional. Note: the dummy backend for !PackageKit provides such metadata, rawhide does not i386 MatthiasClasen Tested with the dummy backend. Works as expected, links are formatted correctly, clicking on them brings up a browser
QA/TestCases/PackageKitNautilusInstall Test that clicking on rpms in nautilus works as expected. x86_64 JamesLaska right-click, open with "Package Installer". Worked for install and updates.
QA/TestCases/PackageKitSignedPackages Test that signed and unsigned packages are handled as expected. i386 MatthiasClasen Tested with local test repositories containing unsigned packages and packages signed with unknown keys. Installation and updates from repositories with gpgcheck=1 both fail for untrusted packages. Installing untrusted packages from local files succeeds. This will change in a future !PackageKit release, when a separate !PolicyKit privilege will be introduced for installation of untrusted packages.

Key

Indicates a test that has passed
Indicates an inprogress or test that needs further review
Indicates a failed test ... see Notes for details

Additional Details