Architectures/ARM/Quality Assurance

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 - installation of guest machine(virt-install) using latest compose. ( triggered by - post-tree-compose)
• rats_sanity - Repository sanity check - tests check repodata, comps.xml validity, core package dependency closure and existence. ( triggered by - post-repo-update )
• repoclosure - ensures packages in a repository have all dependencies satisfied. ( triggered by - post-repo-update )
• rpmguard - compares difference between new and previous package versions, logging important changes only. ( triggered by - post-koji-build)
• rpmlint - checks for common package issues ( triggered by - post-koji-build )
• upgradepath - checks for package version problems in repositories. ( triggered by - post-bodhi-update-batch )

ARM specific tests

Some tests will need to be written specifically for ARM including:

• Image validation
• Individual package tests

Work in progress

• Integration with Bodhi