Skip to content
Virt Test Provider for qemu and other related virtualization backends
Python C C# Shell Makefile Assembly
Branch: master
Clone or download
vivianQizhu Merge pull request #1882 from YanhuiMa/tsc
tsc: add tsc test script for rhel8
Latest commit 686c8a7 Aug 23, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
deps Merge pull request #1793 from PaulYuuu/iperf_func Aug 22, 2019
multi_host_migration Use "six.string_types" instead of "str" Aug 8, 2018
openvswitch Replace test.srcdir with test.workdir Apr 20, 2018
provider cdrom: Support blockdev Aug 5, 2019
qemu Merge pull request #1883 from YanhuiMa/timer_adjust_guest Aug 22, 2019
.gitignore virt: Update .gitignore for guthub tool cache Oct 31, 2013
.gitmodules tools: Add codespell Sep 8, 2013
.pack_exclude virt: Adds file which contain patterns which should be excluded. Apr 1, 2013
.travis.yml bypass ci check errors Jul 19, 2018
CODING_STYLE Fix typos in CODING_STYLE and README Dec 10, 2015
LICENSE Update LICENSE doc Jan 21, 2014
README.rst README.rst: Update inspekt command run by CI Aug 18, 2017
requirements-travis.txt drop simplejson CI check Jun 15, 2018
requirements.txt Modify requirement list May 2, 2018


QEMU test provider for virt-test

This is the official [1] test provider for the following subtest types:

  • QEMU
  • Generic (Virtualization backend agnostic)
  • OpenVSwitch

Really quick start guide

  1. Fork this repo on github
  2. Create a new topic branch for your work
  3. Create a new test provider file in your virt test repo, like:
cp io-github-autotest-qemu.ini myprovider.ini
uri: file:///home/foo/Code/tp-qemu
subdir: generic/
subdir: qemu/
subdir: openvswitch/

You can optionally delete temporarily the io-github-autotest-qemu.ini file, just so you don't have test conflicts. Then you can develop your new test code, run it using virt test, and commit your changes.

  1. Make sure you have inspektor installed.
  2. Run:
inspekt checkall --disable-style E501,E265,W601,E402,E722,E741 --no-license-check
  1. Fix any problems
  2. Push your changes and submit a pull request
  3. That's it.

[1] You can always create your own test provider, if you have special purposes, or just want to develop your work independently.

You can’t perform that action at this time.