Autotest

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Moved install+setup into seperate page)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{lang|en|zh-cn|page=Autotest}}
 +
 
{{header|qa}}
 
{{header|qa}}
{{draft}}
 
  
 
== What is autotest? ==
 
== 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/
+
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: https://github.com/autotest/autotest/wiki
  
 
== How is it used in Fedora? ==
 
== How is it used in Fedora? ==
Line 10: Line 11:
 
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.
 
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 a public autotest instance running at http://autoqa.fedoraproject.org. This instance is hosted by the [[Infrastructure]] team and managed by [[QA]] team. It is not integrated with Fedora account system, so public access to the autotest scheduler web-frontend is not enabledHowever, test results are available and links to results are included in all [https://fedorahosted.org/mailman/listinfo/autoqa-results test result emails].
 
+
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? ==
+
 
+
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? ==
+
 
+
Autotest is currently packaged for [[EPEL]], but due to library dependencies, the package is not yet available for FedoraThe procedure for installing and configuring autotest is detailed in [[Install_and_configure_autotest]]
+
 
+
== How do I add test clients to a autotest server? ==
+
  
{{admon/note|FIXME|This needs more love.  Do we want to discuss ''labels'' and ''platforms'' in this document?}}
+
== How to ... ==
  
For any test clients created through the administrative interface, the autotest service requires passwordless logins in order to access remote test clients.  An RSA key has been created for the autotest user to facilitate passwordless logins.  For any test clients you wish to enable passwordless logins on, type:
+
* [[Install_and_configure_autotest|How to set up my own autotest server?]]
<pre># su - autotest
+
* [[How to add autotest clients]]?
# ssh-copy-id -i $HOME/.ssh/id_rsa.pub  root@client.example.com</pre>
+
* [[How to fix failed autotest clients]]?
 +
* [[Writing AutoQA Tests|How to integrate existing tests?]]
  
[[Category:QA]]
 
 
[[Category:AutoQA]]
 
[[Category:AutoQA]]

Latest revision as of 04:18, 3 June 2013

QA.png


[edit] 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: https://github.com/autotest/autotest/wiki

[edit] 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 a public autotest instance running at http://autoqa.fedoraproject.org. This instance is hosted by the Infrastructure team and managed by QA team. It is not integrated with Fedora account system, so public access to the autotest scheduler web-frontend is not enabled. However, test results are available and links to results are included in all test result emails.

[edit] How to ...