qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: benoit@irqsave.net, Stefan Hajnoczi <stefanha@gmail.com>,
	Jeff Cody <jcody@redhat.com>,
	qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 0/3] Add common QEMU control functionality to qemu-iotests
Date: Tue, 6 May 2014 09:48:55 +0800	[thread overview]
Message-ID: <20140506014855.GB1574@T430.nay.redhat.com> (raw)
In-Reply-To: <20140505153209.GF3317@noname.str.redhat.com>

On Mon, 05/05 17:32, Kevin Wolf wrote:
> Am 05.05.2014 um 17:21 hat Stefan Hajnoczi geschrieben:
> > On Wed, Apr 30, 2014 at 10:55:07AM -0400, Jeff Cody wrote:
> > > This adds some common functionality to control QEMU for qemu-iotests.
> > > 
> > > Additionally, test 085 is updated to use this new functionality.
> > > 
> > > Some minor fixups along the way, to clear up spaced pathname issues, 
> > > for common.rc, test 019, and test 086.
> > > 
> > > 
> > > Jeff Cody (3):
> > >   block: qemu-iotests - add common.qemu, for bash-controlled qemu tests
> > 
> > Once a test launches QEMU, it soon needs to parse QMP commands or wait
> > for QMP events.  That doesn't lend itself to the traditional
> > qemu-iotests shell model.  That is why iotests.py exists.
> > 
> > Shell script is a poor language for test cases that go beyond
> > pre-defined commands whose output is saved for diffing.  The string
> > manipulation is clumsy, JSON is not supported, tricks with fifos can
> > easily deadlock or break when a process terminates unexpectedly, etc.
> > 
> > If we go further in the direction of this patch series, we'll duplicate
> > existing iotests.py code and have complex shell tests that are hard to
> > extend.  I think it's time to draw the line and convert any test cases
> > that need to complexity to Python.
> > 
> > Why not use iotests.py?
> 
> Because it's hard to use. The "compare against reference output" thing
> is the first thing that you lose with iotests.py, and it's the most
> useful feature in qemu-iotests.
> 
> When a Python test case fails, you get into real debugging. When a shell
> script test case fails, you usually see immediately from the reference
> output diff what's wrong.
> 

Perhaps we should add more error information into iotests.py, if a test case
fails.

Otherwise I don't think iotests.py hard to use though, out of my subjective
point. I agree that shell is not as goog as python in this kind of test.

Fam

  parent reply	other threads:[~2014-05-06  1:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1398869041.git.jcody@redhat.com>
2014-05-05 15:21 ` [Qemu-devel] [PATCH v5 0/3] Add common QEMU control functionality to qemu-iotests Stefan Hajnoczi
2014-05-05 15:32   ` Kevin Wolf
2014-05-05 15:44     ` Jeff Cody
2014-05-06  8:35       ` Stefan Hajnoczi
2014-05-06  1:48     ` Fam Zheng [this message]
2014-05-06  8:29     ` Stefan Hajnoczi
2014-05-06  8:51       ` Kevin Wolf
2014-05-06 14:06         ` Stefan Hajnoczi
2014-05-09 15:49 ` Stefan Hajnoczi

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=20140506014855.GB1574@T430.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=benoit@irqsave.net \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).