|
|
| (5 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| = KVM-Autotest = | | = KVM-Autotest = |
|
| |
|
| The KVM-Autotest system is a client test for the [http://autotest.kernel.org/ autotest] framework. Its main purpose is to serve as an automated regression testing tool for KVM developers, and for doing regular automated testing of KVM (provided you use it with the server testing infrastructure).
| | KVM autotest and virt-test are the former names of a set of virtualization tests that include KVM and other virtualization backends on Linux platforms. Now the project is known as Avocado and Avocado-VT. |
|
| |
|
| Autotest is a project that aims to provide tools and libraries to perform automated testing on the linux platform. KVM autotest is a subproject under the autotest umbrella. For more information on autotest, see http://autotest.kernel.org/. Autotest is a modular framework, and KVM autotest is nothing more than a submodule of the client module. Of course, for more complex testing we also use other parts of autotest, and for centralized tests, we deploy a full autotest infrastructure.
| | == Avocado and Avocado-VT == |
|
| |
|
| KVM autotest aims to be a centralizing project for most of the KVM functional and performance testing needs. We cover:
| | These are the current community projects that have come from a long heritage, including virt-test and KVM-Autotest. |
|
| |
|
| * Guest OS install, for both Windows (WinXP - Win7) and Linux (RHEL, Fedora, OpenSUSE and others through step engine mechanism)
| | Avocado is a generic testing framework, while Avocado-VT adds support for Virtualization testing (a continuation of virt-test). |
| * Serial output for Linux guests
| |
| * Migration, networking, timedrift and other types of tests
| |
| * Monitor control for both human and QMP protocols
| |
| * Build and use qemu using various methods (source tarball, git repo, rpm)
| |
| * Some level of performance testing can be made.
| |
| * The KVM unit tests can be run comfortably from inside kvm autotest, we do have full integration with the unittest execution
| |
|
| |
|
| We support x86_64 hosts with hardware virtualization support (AMD and Intel), and Intel 32 and 64 bit guest operating systems.
| | To get started with Avocado-VT please visit: |
|
| |
|
| For an overview about KVM autotest, how this project was created, its goals, structure, and how to develop simple tests, you can refer to the [http://vimeo.com/15234614 KVM forum 2010 presentation], [[Media:2010-forum-Kvm-autotest.pdf | Slides]]
| | http://avocado-vt.readthedocs.io |
|
| |
|
| * [[KVM-Autotest/Getting Started|Getting Started with KVM testing]] - How to get your first tests up and running.
| | https://github.com/avocado-framework/avocado-vt |
| * [[KVM-Autotest/Cmdline|Using the autotest command line]] - How to use the autotest cli to run your kvm tests in an easier way
| |
| * [[KVM-Autotest/Test Config File|The test configuration file format]] - How to work with the framework configuration file format.
| |
|
| |
|
| * [[KVM-Autotest/Tests|KVM subtest reference]] - Brief overview of the available test API.
| |
| * [[KVM-Autotest/Contributing|Contribute to KVM autotest]] - Guidance on how to submit patches.
| |
|
| |
|
| * [[KVM-Autotest/Parameters|Framework parameters]] - Lists and explains the parameters used by the framework.
| | To learn more about Avocado please visit: |
|
| |
|
| * [[KVM-Autotest/AddNewGuests|Adding New Step files]] - The default install mode for most guests now is the unattended install, but for some guests, we might need to use step based install. This explains how to do so.
| | http://avocado-framework.readthedocs.io |
|
| |
|
| ---- | | https://github.com/avocado-framework/avocado |
|
| |
|
| * [[KVM-Autotest/TODO|TODO]] - TODO list, for those interested in helping.
| | [[Category:Redirects]][[Category:Testing]] |