descriptionZhi Yong Wu's KVM-autotest tree
homepage URL
last changeFri, 8 Jul 2011 18:05:22 +0000 (8 18:05 +0000)
content tags
Autotest: Fully automated tests under the linux platform

Autotest is a framework for fully automated testing. It is designed primarily to
test the Linux kernel, though it is useful for many other functions such as
qualifying new hardware. It's an open-source project under the GPL and is used
and developed by a number of organizations, including Google, IBM, Red Hat, and
many others.

Autotest is composed of a number of modules that will help you to do stand alone
tests or setup a fully automated test grid, depending on what you are up to.
A non extensive list of modules is:

* Autotest client: The engine that executes the tests (dir client). Each
autotest test is a a directory inside (client/tests) and it is represented
by a python class that implements a minimum number of methods. The client
is what you need if you are a single developer trying out autotest and executing
some tests. Autotest client executes ''client side control files'', which are
regular python programs, and leverage the API of the client.

* Autotest server: A program that copies the client to remote machines and
controls their execution. Autotest server executes ''server side control files'',
which are also regular python programs, but leverage a higher level API, since
the autotest server can control test execution in multiple machines. If you
want to perform tests slightly more complex involving more than one machine you
might want the autotest server

* Autotest database: For test grids, we need a way to store test results, and
that is the purpose of the database component. This DB is used by the autotest
scheduler and the frontends to store and visualize test results.

* Autotest scheduler: For test grids, we need an utility that can schedule and
trigger job execution in test machines, the autotest scheduler is that utility.

* Autotest web frontend: For test grids, A web app, whose backend is written in
django ( and UI written in gwt
(, lets users to trigger jobs and visualize
test results

* Autotest command line interface: Alternatively, users also can use the
autotest CLI, written in python

Getting started with autotest client

For the impatient:

Check out the main project documentation source

You can find plenty of information on the autotest wiki

That also contains references to the project activity

Links to an online view of the version control system

Grabbing the latest source

Hacking and submitting patches

Downloading stable versions
2011-07-08 lmrvirt.virt_test_utils: run_autotest - 'tar' needs relati... master
2011-07-08 lmrfsdev_disks.get_disk_list(): Add option to get unpartit...
2011-07-07 lmrFix various packager issues. Add options to global_config
2011-07-07 lmrcommon_lib.base_packages: Add parallel bzip2 support...
2011-07-07 lmrcommon_lib.logging_config: Fix wrong exception class...
2011-07-07 lmrcommon_lib.logging_config: Ignore KeyError on double...
2011-07-06 lmrKVM test: Fix missing commas and unattended install...
2011-07-06 lmrKVM test: Add new virtio-win.cfg.sample file
2011-07-05 lmrKVM test: Don't restrict Windows guests on virtio_blk...
2011-07-05 lmrKVM test: A couple of fixes for unattended install
2011-07-05 lmrKVM test: Add subtest smbios_table
2011-07-05 lmrweb backend: Fix for adding acl groups in Django Admin
2011-07-04 lmrKVM Test: drop support for building/loading external...
2011-07-04 lmrvirt: Add more flexible way to specify comm ports host...
2011-07-04 lmrKVM test: Reformat sample windows ini style unattended...
2011-07-04 lmrKVM test: Update Win2003 CD info to match MSDN shipped CD
7 years ago io_limits
7 years ago master