Autotest

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Add to AutoQA category)
(Move some test-specific stuff to the Writing AutoQA Tests page)
Line 7: Line 7:
  
 
== How is it used in Fedora? ==
 
== How is it used in Fedora? ==
 +
 +
We're currently using it as the test harness for [[AutoQA]]. It handles the dirty work of getting code onto test machines, running it, and holding all the results.
  
 
Currently there is no public autotest instance. The [[QA]] team has been working on [https://fedorahosted.org/autoqa/ticket/9 packaging autotest] for use in the Fedora infrastructure.
 
Currently there is no public autotest instance. The [[QA]] team has been working on [https://fedorahosted.org/autoqa/ticket/9 packaging autotest] for use in the Fedora infrastructure.
  
We're planning to use it as the test harness for [https://fedorahosted.org/autoqa/ AutoQA], starting with the [[Israwhidebroken.com Proposal]]. In the future we may open it up to allow all Fedora contributors to write tests and have them be run automatically.
+
The [[AutoQA]] project is starting out by using it to automate some existing tests (like <code>repoclosure</code> from {{package|yum-utils}}) and some new tests from the [[Israwhidebroken.com Proposal]].  
  
 
== How do I write a test for autotest? ==
 
== How do I write a test for autotest? ==
  
The short version:
+
Start by writing some test code in whatever language(s) you feel comfortable with. Don't even worry about autotest or [[AutoQA]] until you have a functioning test. Once you do, see [[Writing AutoQA Tests]] for more info.
# Write a test. You can write it in whatever language you're comfortable with.
+
# Create a control file. This gives autotest some metadata about the test.
+
#* Some control file requirements are listed under [http://autotest.kernel.org/wiki/ControlRequirements ControlRequirements] on the autotest wiki.
+
# Create a test script. This runs your test program and reports back the results.
+
#* The test scripts are written in Python; see [http://autotest.kernel.org/wiki/AddingTest AddingTest] and [http://autotest.kernel.org/wiki/AutotestApi AutotestAPI] on the autotest wiki for details.
+
# Create a new dir in the autoqa git tree for your test.
+
#* The details of this process have yet to be finalized.
+
 
+
=== Writing a test ===
+
TODO
+
 
+
=== Writing a control file ===
+
TODO
+
  
=== Writing the test script ===
+
== How do I set up my own autotest server? ==
TODO
+
  
=== Checking in the new test ===
+
Docs in progress - see [https://fedorahosted.org/autoqa/ticket/5 this trac ticket]
TODO
+
  
 
[[Category:QA]]
 
[[Category:QA]]
 
[[Category:AutoQA]]
 
[[Category:AutoQA]]

Revision as of 16:25, 26 August 2009

QA.png


Warning (medium size).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.

Contents

What is autotest?

Autotest is "a framework for automated testing". It gives us a way to run automated tests and collect results. For more information, see their wiki: http://autotest.kernel.org/

How is it used in Fedora?

We're currently using it as the test harness for AutoQA. It handles the dirty work of getting code onto test machines, running it, and holding all the results.

Currently there is no public autotest instance. The QA team has been working on packaging autotest for use in the Fedora infrastructure.

The AutoQA project is starting out by using it to automate some existing tests (like repoclosure from Package-x-generic-16.pngyum-utils) and some new tests from the Israwhidebroken.com Proposal.

How do I write a test for autotest?

Start by writing some test code in whatever language(s) you feel comfortable with. Don't even worry about autotest or AutoQA until you have a functioning test. Once you do, see Writing AutoQA Tests for more info.

How do I set up my own autotest server?

Docs in progress - see this trac ticket