Revision as of 13:54, 20 September 2012

Introduction

AutoQA is an automated test system for Fedora. Its design is simple: when certain events occur, AutoQA launches automated tests. Events that AutoQA monitors include:

New packages in the koji build system
New Fedora updates submitted through bodhi
Updated package repositories for rawhide, the current branched release (Fedora 41), and previous Fedora releases
Updated installable images of the current branched release (Fedora 41)

Get Involved

Just looking? Follow the links below for general information on the AutoQA project.

Examine the current list of tests
Review the current test events being monitored
Review recent test results or sign-up for test result notification

Interested in writing tests?

Read Writing AutoQA Tests and Verifying AutoQA tests
Should your test require a new method to trigger testing, read Writing AutoQA Events and Watchers (optional)
Integrate your test with AutoQA - Install and configure AutoQA

How about contributing back to the AutoQA project?

Familiarize yourself with the architecture overview and development roadmap
Checkout the code -- autoqa.git
AutoQA uses the Autotest test harness, learn more by visiting Autotest
AutoQA also has a set of self tests that could always be expanded.

Communicate

Please contact us! We look forward to your ideas and suggestions.

autoqa-devel is the mailing list for development discussion of the AutoQA project
autoqa-results is where automated test results are submitted. This is intended for test results review only.
Talk about AutoQA on the permanent QA IRC channel #fedora-qa^[?]
Visit the project development page at https://fedorahosted.org/autoqa/

@@ Line 1: / Line 1: @@
-{{draft}}
+[[Image:Autoqa_logo.png|center]]
-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.
-== Events and Hooks ==
+= Introduction =
+'''AutoQA''' is an automated test system for Fedora.  Its design is simple: when certain events occur, AutoQA launches automated tests.  Events that AutoQA monitors include:
-For AutoQA to respond to an event, someone needs to write a "hook" for that event. The first step in creating a new hook is, obviously, to define the event it responds to.
+* New packages in the [http://koji.fedoraproject.org koji build system]
+* New Fedora updates submitted through [https://admin.fedoraproject.org/updates bodhi]
+* Updated package repositories for [[Releases/Rawhide|rawhide]], the current [[Releases/Branched|branched]] release ({{FedoraVersion|long|next}}), and previous Fedora releases
+* Updated installable images of the current [[Releases/Branched|branched]] release ({{FedoraVersion|long|next}})
-For example, the <code>post-repo-update</code> hook is triggered whenever a Fedora repo is updated. Obviously, any test that will run in response to this event will need to know the URL of the repo that was just updated. (This is a <i>required</i> argument.) Certain repos can't be used properly without other "parent" repos (for example, the Fedora 11 <code>updates</code> repo isn't useful without also knowing the address of the main Fedora 11 repo). So a list of "parent repos" is an <i>optional argument</i> to the tests.
+= Get Involved =
-Detailed information about implementing new hooks can be found in [[Writing AutoQA Hooks]].
+Just looking?  Follow the links below for general information on the AutoQA project.
-== The autoqa Harness ==
+* Examine [http://git.fedorahosted.org/cgit/autoqa.git/tree/tests the current list of tests]
+* Review [http://git.fedorahosted.org/cgit/autoqa.git/tree/events the current test events being monitored]
+* Review [https://fedorahosted.org/pipermail/autoqa-results/{{CURRENTYEAR}}-{{CURRENTMONTHNAME}}/thread.html recent test results] or [http://jlaska.wordpress.com/2010/06/01/fedora-package-maintainers-want-test-results/ sign-up for test result notification]
-The autoqa harness is launched by the watchers in response to an event.
+Interested in writing tests?
+* Read [[Writing AutoQA Tests]] and [[Verifying AutoQA tests]]
+* Should your test require a new method to trigger testing, read [[Writing AutoQA Events and Watchers]] ''(optional)''
+* Integrate your test with AutoQA - [[Install and configure AutoQA]]
+How about contributing back to the AutoQA project?
+* Familiarize yourself with the [[AutoQA_architecture|architecture overview]] and [[AutoQA_Roadmap|development roadmap]]
+* Checkout the code -- [http://git.fedorahosted.org/git/?p=autoqa.git;a=summary autoqa.git]
+* AutoQA uses the [[Autotest]] test harness, learn more by visiting [[Autotest]]
+* AutoQA also has a set of [[AutoQA_Self_Testing|self tests]] that could always be expanded.
+= Communicate =
+Please contact us!  We look forward to your ideas and suggestions.
+* [https://fedorahosted.org/mailman/listinfo/autoqa-devel autoqa-devel] is the mailing list for development discussion of the AutoQA project
+* [https://fedorahosted.org/mailman/listinfo/autoqa-results autoqa-results] is where automated test results are submitted.  This is intended for test results review only.
+* Talk about AutoQA on the permanent QA IRC channel {{fpchat|#fedora-qa}}
+* Visit the project development page at https://fedorahosted.org/autoqa/
 [[Category:AutoQA]]

Search

AutoQA: Difference between revisions

Revision as of 13:54, 20 September 2012

Introduction

Get Involved

Communicate