From Fedora Project Wiki
 
(25 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Introduction =
= ARM QA =  
= AutoQA =
AutoQA is the automated test system used in Fedora. <b>Watchers</b> (scheduled through cron ) look for <b>Events</b> ( eg - new package built in Koji, new repo has finished, creation of new installable images, updates in bodhi ). Once an <b>event</b> occurs it triggers automated tests.


== Current Events monitored ==
== Release Criteria ==
*git-post-receive - tests run after action performed in git.
*post-bodhi-update - update in Bodhi requests to be moved in 'testing' or 'stable'.
*post-bodhi-update-batch
*post-koji-build - new package built in Koji.
*post-koji-build-batch
*post-repo-update - change in repository package contents or metadata.
*post-tree-compose - new tree compose ( installation/boot images, package repository and metadata )


== Current Tests ==
===Fedora 19===
*conflicts - checks for package conflicts. Runs potential_conflict from yum-utils. ( triggered by - post-repo-update )
ARM used the Primary Architecture release criteria for Fedora 19
*depcheck - checks to see if package would cause broken dependencies if pushed to live repositories. ( triggered by - post-bodhi-update event )
* [[Fedora_19_Alpha_Release_Criteria | Alpha]]
*rats_install - installation of guest machine(virt-install) using latest compose. ( triggered by - post-tree-compose)
* [[Fedora_19_Beta_Release_Criteria | Beta]]
*rats_sanity - Repository sanity check - tests check repodata, comps.xml validity, core package dependency closure and existence. ( triggered by - post-repo-update )
* [[Fedora_19_Final_Release_Criteria | Final]]
*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 ==
===Fedora 18===
Some tests will need to be written specifically for ARM including:
ARM specific release criteria, based on Primary Architecture, wording and tests adjusted.
* Image validation
* [[Architectures/ARM/Fedora_18_Alpha_Release_Criteria | Alpha]]
* Individual package tests
* [[Architectures/ARM/Fedora_18_Beta_Release_Criteria | Beta]]
* [[Architectures/ARM/Fedora_18_Final_Release_Criteria | Final]]


= Hardware Access & Repair =
===Fedora 17===
Currently not everyone working within Fedora has access to an ARM device so it necessary to provide access to developers to test their software. Once their testing is completed, the device needs to be restored to a pristine state. At this time Anaconda is not fully functional, so some possible solutions include:
*SD card switch - allows access to be transferred remotely from card reader to ARM device, allowing for remote machine repair.
*QEMU


= Work in progress =
== Release Validation Testing ==
* Integration with Bodhi
===Rawhide===
* [[Architectures/ARM/Quality Assurance/Rawhide |Rawhide Images]]
 
===Fedora 19===
Fedora 19 release validation testing followed the PA matrices, adjusting to ARM where appropriate.
* [[:Category:Fedora 19 ARM RC3|Fedora 19 ARM RC3]] (final)
* [[:Category:Fedora 19 ARM RC2|Fedora 19 ARM RC2]]
 
* [[:Category:Fedora 19 ARM TC6|Fedora 19 ARM TC6]]
* [[:Category:Fedora 19 ARM TC5|Fedora 19 ARM TC5]]
* [[:Category:Fedora 19 ARM TC3|Fedora 19 ARM TC3]]
* [[:Category:Fedora 19 ARM TC2|Fedora 19 ARM TC2]]
* [[:Category:Fedora 19 ARM TC1|Fedora 19 ARM TC1]]
 
* [[:Category:Fedora 19 ARM Beta|Fedora 19 ARM Beta]]
 
===Fedora 18===
Fedora 18 used VFAD style testing, with ARM specific matrices based on Release Criteria. Testing similar to PA testing.
* [[Architectures/ARM/Quality Assurance/2013-05-21-VFAD-Fedora 19 Beta RC2|Fedora 18 RC2]]
* [[Architectures/ARM/Quality Assurance/2013-02-01-VFAD-Fedora 18 RC1|Fedora 18 RC1]]
* [[Architectures/ARM/Quality Assurance/2012-12-20-VFAD-Fedora 18 Beta|Fedora 18 Beta RC2]]
* [[Architectures/ARM/Quality Assurance/2012-12-03-VFAD-Fedora 18 Beta|Fedora 18 Beta RC1]]
* [[Architectures/ARM/Quality Assurance/2012-10-26-VFAD-Fedora 18 Test Day|Fedora 18 ARM VFAD - TC2]]
* [[Architectures/ARM/Quality Assurance/2012-10-15-VFAD-Fedora 18 Test Day|Fedora 18 ARM VFAD - TC1]]
 
===Fedora 17===
Fedora 17 used VFAD style testing, with ARM specific matrices based on Release Criteria. Testing similar to PA testing.
* [[Architectures/ARM/Quality Assurance/2012-06-18-VFAD-Fedora 17 Test Day|Fedora 17 ARM VFAD - RC2]]
* [[Architectures/ARM/Quality_Assurance/2012-06-15-VFAD-Fedora_17_Test_Day|Fedora 17 ARM VFAD - RC1]]
 
== Kernel Testing ==
ARM kernel testing on various supported platforms.
* [[Architectures/ARM/Quality_Assurance/Kernel_Testing/Fedora_20 |Fedora 20]]
* [[Architectures/ARM/Quality_Assurance/Kernel_Testing/Fedora_19 |Fedora 19]]
* [[Architectures/ARM/Quality_Assurance/Kernel_Testing/Fedora_18 |Fedora 18]]
* [[Architectures/ARM/Quality_Assurance/Kernel_Testing/Fedora_17 |Fedora 17]]
* [[Architectures/ARM/Quality_Assurance/Kernel_Testing/Archive|Archive of Older Kernels]]

Latest revision as of 20:08, 9 August 2013

ARM QA

Release Criteria

Fedora 19

ARM used the Primary Architecture release criteria for Fedora 19

Fedora 18

ARM specific release criteria, based on Primary Architecture, wording and tests adjusted.

Fedora 17

Release Validation Testing

Rawhide

Fedora 19

Fedora 19 release validation testing followed the PA matrices, adjusting to ARM where appropriate.

Fedora 18

Fedora 18 used VFAD style testing, with ARM specific matrices based on Release Criteria. Testing similar to PA testing.

Fedora 17

Fedora 17 used VFAD style testing, with ARM specific matrices based on Release Criteria. Testing similar to PA testing.

Kernel Testing

ARM kernel testing on various supported platforms.

Retrieved from "https://fedoraproject.org/w/index.php?title=Architectures/ARM/Quality_Assurance&oldid=348655"