From Fedora Project Wiki
(template) |
(first version) |
||
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 test to ensure that the [[Critical Path Packages Proposal|Critical Path Packages]] have no missing dependencies or package/file conflicts. | |description=A test to ensure that the [[Critical Path Packages Proposal|Critical Path Packages]] have no missing dependencies or package/file conflicts. | ||
Note that this test only checks the package metadata; [[QA:Core package existence test case]] confirms that the packages actually exist in the repo. | |||
|actions= | |actions= | ||
# | # Obtain (or generate) a current list of the critical path packages | ||
# | #* '''Note''': The procedure for this isn't finalized but it will work something like: | ||
# | #*# Fetch this script: [http://wwoods.fedorapeople.org/files/critical-path/resolve_out_deps.py resolve_out_deps.py] | ||
#*# Run: <code>resolve_out_deps.py $RAWHIDE_URL</code> | |||
# Ensure that all the dependencies for all the packages listed are satisfied | |||
#* This will be handled automatically by <code>resolve_out_deps.py</code> | |||
# Ensure that there are no conflicts between any of the packages listed | |||
#* This is also handled automatically by <code>resolve_out_deps.py</code> | |||
|results= | |results= | ||
# <code>resolve_out_deps.py</code> reports no conflicts or missing dependencies | |||
}} | }} |
Revision as of 21:43, 8 July 2009
Description
A test to ensure that the Critical Path Packages have no missing dependencies or package/file conflicts.
Note that this test only checks the package metadata; QA:Core package existence test case confirms that the packages actually exist in the repo.
How to test
- Obtain (or generate) a current list of the critical path packages
- Note: The procedure for this isn't finalized but it will work something like:
- Fetch this script: resolve_out_deps.py
- Run:
resolve_out_deps.py $RAWHIDE_URL
- Note: The procedure for this isn't finalized but it will work something like:
- Ensure that all the dependencies for all the packages listed are satisfied
- This will be handled automatically by
resolve_out_deps.py
- This will be handled automatically by
- Ensure that there are no conflicts between any of the packages listed
- This is also handled automatically by
resolve_out_deps.py
- This is also handled automatically by
Expected Results
resolve_out_deps.py
reports no conflicts or missing dependencies