You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Yanan Fu a1a3b4f559
Merge pull request #2173 from huangyum/cpu_host
2 days ago
deps ovs_host_vlan: fix netperf issue and kill vm at the end of the test 4 months ago
generic Merge pull request #2009 from YongxueHong/bug-1566862 1 month ago
multi_host_migration Use "six.string_types" instead of "str" 1 year ago
openvswitch Replace test.srcdir with test.workdir 1 year ago
provider Merge pull request #2161 from xutian/top_sync 2 days ago
qemu Merge pull request #2173 from huangyum/cpu_host 2 days ago
.gitignore virt: Update .gitignore for guthub tool cache 6 years ago
.gitmodules tools: Add codespell 6 years ago
.pack_exclude virt: Adds file which contain patterns which should be excluded. 7 years ago
.travis.yml bypass ci check errors 1 year ago
CODING_STYLE Fix typos in CODING_STYLE and README 4 years ago
LICENSE Update LICENSE doc 6 years ago
README.rst README.rst: Update inspekt command run by CI 2 years ago
requirements-travis.txt drop simplejson CI check 1 year ago
requirements.txt Modify requirement list 1 year ago


QEMU test provider for virt-test

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

* 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,


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.

4) Make sure you have `inspektor installed. <>`_
5) Run:


inspekt checkall --disable-style E501,E265,W601,E402,E722,E741 --no-license-check

6) Fix any problems
7) Push your changes and submit a pull request
8) 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.