From Fedora Project Wiki

(template)
 
(add to Category:Rawhide Acceptance Test Cases)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{admon/warning|Work in progress|This test case involves the [[Critical Path Packages Proposal|Critical Path packages]]. The package list is still being defined and the tools for generating the list are not yet complete. This test will change as the tools and package list are updated.}}
{{admon/warning|Work in progress|This test case involves the [[Critical Path Packages Proposal|Critical Path packages]]. The package list is still being defined and the tools for generating the list are not yet complete. This test will change as the tools and package list are updated.}}
{{QA/Test_Case
{{QA/Test_Case
|description=A simple test to check that the [[Critical Path Packages Proposal|Critical Path]] packages are available in the repo and not corrupt.
|description=A test to ensure that the [[Critical Path Packages Proposal|Critical Path Packages]] are present and not corrupted.
|actions=
|actions=
# TODO
# Obtain (or generate) a current list of the critical path packages
# Next do this ...
#* '''Note''': The procedure for this isn't finalized but the list of packages should be generated as a side-effect of the [[QA:Core package dependency closure test case]]
# Finally click that
# Check that all the listed packages are present in the repo
# Check that all the listed packages match their embedded checksums and/or GPG signatures
#* <code>rpm -Vp $RPM_NAME</code> will do this nicely
|results=
|results=
The following must be true to consider this a successful test run. Be brief ... but explicit.
# All critical path packages are present and match their checksums and/or GPG signatures
# Step #1 completes without error
# The system boots into runlevel 5
# Program completes wth exit code 0
}}
}}
[[Category:Rawhide Acceptance Test Cases]]

Latest revision as of 20:41, 13 July 2009

Work in progress
This test case involves the Critical Path packages. The package list is still being defined and the tools for generating the list are not yet complete. This test will change as the tools and package list are updated.

Description

A test to ensure that the Critical Path Packages are present and not corrupted.


How to test

  1. Obtain (or generate) a current list of the critical path packages
  2. Check that all the listed packages are present in the repo
  3. Check that all the listed packages match their embedded checksums and/or GPG signatures
    • rpm -Vp $RPM_NAME will do this nicely

Expected Results

  1. All critical path packages are present and match their checksums and/or GPG signatures