From Fedora Project Wiki

Revision as of 13:58, 18 November 2009 by Kparal (talk | contribs) (completely reworked - provided basic information about the project and linked more advanced articles; most of the previous text moved to "AutoQA architecture")

QA.png


Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.

AutoQA is an automated test system for Fedora. Its basic design is simple: when certain events occur (a package is built, updates are pushed, a new Rawhide build is available, etc.) AutoQA launches some automated tests.

Visit the project development page at: https://fedorahosted.org/autoqa/

How does it work

End users

End users are those people, who use AutoQA just to see the result of a particular test. They will probably be developers (of other software) at the same time.

If you work with development version of Fedora, AutoQA results page will inform you if the up-to-date Rawhide repository is broken or not, if the Rawhide is installable and bootable, etc. If you maintain some packages for Fedora, you can see there if there were some problems detected with latest updates of your packages or not. We plan to provide means of notifications to the package maintainer if such events happens.

The public website will be set up in a near future and will display every-day results of tests performed. Currently you can see output of all the tests executions posted in the autoqa-results list.

Developers

Developers are those people, who have intentions to work on AutoQA itself or want to contribute another test for it.

The internal layout of AutoQA itself is described in AutoQA architecture. If you plan to write a new test, please see Writing AutoQA Tests. Instructions for installing and setting up AutoQA on your own machine are available in Installing AutoQA.

More documentation

Other documentation about AutoQA on this wiki can be found at Category:AutoQA.

Providing feedback

Please contact us! The most recommended way is writing to autoqa-devel list, but you can also use fedora-test-list or #fedora-qa channel.