From: Dor Laor <dlaor@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC v2 0/6] qtest unit test framework
Date: Sun, 04 Dec 2011 12:03:48 +0200 [thread overview]
Message-ID: <4EDB4584.8020606@redhat.com> (raw)
In-Reply-To: <1322765012-3164-1-git-send-email-aliguori@us.ibm.com>
On 12/01/2011 08:43 PM, Anthony Liguori wrote:
> This series is still pretty rough but I wanted to get an idea of what people
> thought about it before polishing it.
>
> The general idea is outlined in the first test. The main advantage of this
> type of test framework compared to something like kvm-unit-test is that you
> don't need a build environment for what you're trying to test.
Luckily w/ qemu cpu emulation and few images it can be set once and be
there for ever.
The advantage of kvm-unit-test is that the code actually does run. So we
can test irq injections, io/mmio in the kernel too, dirty bit tracking
and some more all together.
>
> Since your tests also link against the host environment, it potentially makes
> tests much simplier to write (as you aren't reinventing an OS). I think this
> makes this style of test more appropriate for something like QEMU.
>
> Anthony Liguori (6):
> qtest: add test framework
> qtest: add support for target-i386 -M pc
> Add core python test framework
> Add uart test case
> Add RTC test case
> Add C version of rtc-test
>
> Makefile | 4 +
> Makefile.objs | 2 +
> hw/pc.c | 7 +-
> hw/pc_piix.c | 9 +-
> qemu-options.hx | 8 ++
> qtest.c | 357 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> qtest.h | 37 ++++++
> qtest.py | 69 +++++++++++
> rtc-test.c | 201 +++++++++++++++++++++++++++++++
> rtc-test.py | 105 ++++++++++++++++
> serial-test.py | 24 ++++
> vl.c | 8 ++
> 12 files changed, 827 insertions(+), 4 deletions(-)
> create mode 100644 qtest.c
> create mode 100644 qtest.h
> create mode 100644 qtest.py
> create mode 100644 rtc-test.c
> create mode 100644 rtc-test.py
> create mode 100644 serial-test.py
>
next prev parent reply other threads:[~2011-12-04 10:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 18:43 [Qemu-devel] [RFC v2 0/6] qtest unit test framework Anthony Liguori
2011-12-01 18:43 ` [Qemu-devel] [RFC v2 1/6] qtest: add " Anthony Liguori
2011-12-05 14:27 ` Luiz Capitulino
2011-12-01 18:43 ` [Qemu-devel] [RFC v2 2/6] qtest: add support for target-i386 -M pc Anthony Liguori
2011-12-02 7:52 ` Paolo Bonzini
2011-12-29 17:40 ` Peter Maydell
2011-12-29 18:47 ` Anthony Liguori
2011-12-01 18:43 ` [Qemu-devel] [RFC v2 3/6] Add core python test framework Anthony Liguori
2011-12-01 18:43 ` [Qemu-devel] [RFC v2 4/6] Add uart test case Anthony Liguori
2011-12-01 18:43 ` [Qemu-devel] [RFC v2 5/6] Add RTC " Anthony Liguori
2011-12-05 14:32 ` Luiz Capitulino
2011-12-01 18:43 ` [Qemu-devel] [RFC v2 6/6] Add C version of rtc-test Anthony Liguori
2011-12-02 17:25 ` Kevin Wolf
2011-12-02 17:26 ` Anthony Liguori
2011-12-02 17:45 ` Kevin Wolf
2011-12-02 18:20 ` Luiz Capitulino
2011-12-02 18:43 ` Anthony Liguori
2011-12-05 8:51 ` Kevin Wolf
2011-12-04 10:03 ` Dor Laor [this message]
2011-12-05 15:29 ` [Qemu-devel] [RFC v2 0/6] qtest unit test framework Anthony Liguori
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=4EDB4584.8020606@redhat.com \
--to=dlaor@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.