From Fedora Project Wiki
< Architectures | ARM
| Line 13: | Line 13: | ||
== Current Tests == | == Current Tests == | ||
*conflicts - checks for package conflicts | *conflicts - checks for package conflicts. Runs potential_conflict from yum-utils. ( triggered by - post-repo-update ) | ||
*depcheck - checks to see if package would cause broken dependencies if pushed to live repositories. ( triggered by - post-bodhi-update event ) | *depcheck - checks to see if package would cause broken dependencies if pushed to live repositories. ( triggered by - post-bodhi-update event ) | ||
*rats_install - | *rats_install - | ||
Revision as of 03:12, 18 April 2012
Introduction
AutoQA
AutoQA is the automated test system used in Fedora. Watchers (scheduled through cron ) look for Events ( eg - new package built in Koji, new repo has finished, creation of new installable images, updates in bodhi ). Once an event occurs it triggers automated tests.
Current Events monitored
- git-post-receive
- post-bodhi-update-batch
- post-bodhi-update
- post-koji-build-batch
- post-koji-build
- post-repo-update
- post-tree-compose
Current Tests
- conflicts - checks for package conflicts. Runs potential_conflict from yum-utils. ( triggered by - post-repo-update )
- depcheck - checks to see if package would cause broken dependencies if pushed to live repositories. ( triggered by - post-bodhi-update event )
- rats_install -
- rats_sanity
- repoclosure
- rpmguard
- rpmlint
- upgradepath
ARM specific tests
Some tests will need to be written specifically for ARM including:
- Image validation
Hardware Access & Repair
Work in progress
- Integration with Bodhi