public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Zhu Yijun <zhuyijun@huawei.com>
Cc: kvm@vger.kernel.org, oscar.zhangbo@huawei.com,
	Hangaohuai <hangaohuai@huawei.com>
Subject: Re: questions about kvm test
Date: Fri, 26 Feb 2016 15:26:07 +0100	[thread overview]
Message-ID: <20160226142603.GA17211@potion.redhat.com> (raw)
In-Reply-To: <56CD7BAC.4070807@huawei.com>

2016-02-24 17:45+0800, Zhu Yijun:
> Hi all,
> 
>   I am getting start with kvm, and interest in kvm auto test. Currently I have found two related projects, one is kvm-unit-tests, and the other is avocado-vt.
> 
>   So my question is:
> 
>   1) If there is relationship between above two test suite?

They have different goals, but it makes sense to run kvm-unit-tests
inside avocado.

kvm-unit-tests is a collection of single-purpose guests that test some
parts of KVM (the kernel).  kvm-unit-tests also contain a simple
framework to let you run those guests without hassle.

avocado-vt is a module for avocado testing framework that allows you to
conveniently automate tests about and inside guests.  avocado-vt also
collects tests for guest that run on KVM.

>   1)                                                        We should use them alone or together?

If you would be using avocado anyway, then it's a good idea to run
kvm-unit-tests from it, instead of running them separately.

(I presume that you'll run something, like jenkins, on top of avocado,
 so having just one set of results will be simpler.)

>   2) Is there any other kvm test suite available?

That depends on what you count and what you actually want to test.
Working with KVM guests is testing KVM. :)

Virtualization mostly emulates real hardware, so pretty much any
hardware test suite is worthwhile and other components in your virt
stack (QEMU, libvirt, ...) have a specialized test suites that also
exercise KVM.

AFAIK avocado(-vt) is the latest try at THE testing framework, so using
it should be more convenient than writing your own framework to test a
huge cartesian product of variables that KVM+QEMU+libvirt+... provides.

>   2)                                              And which one is mainly used at present?

I guess that developers mostly use the test suite for their project or
custom tests/benchmarks that cover their current work.

Autotest maybe still is the most popular framework, but avocado
obsoletes it.

Btw. the avocado team will be able to provide much better information.

  reply	other threads:[~2016-02-26 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  9:45 questions about kvm test Zhu Yijun
2016-02-26 14:26 ` Radim Krčmář [this message]
2016-02-27  1:01   ` Zhu Yijun
2016-02-28  0:09     ` Amos Jianjun Kong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160226142603.GA17211@potion.redhat.com \
    --to=rkrcmar@redhat.com \
    --cc=hangaohuai@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=oscar.zhangbo@huawei.com \
    --cc=zhuyijun@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox