qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Cody <jcody@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Markus Armbruster <armbru@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] What tests should "make check-block" run?
Date: Thu, 28 Aug 2014 11:22:31 -0400	[thread overview]
Message-ID: <20140828152231.GA11815@localhost.localdomain> (raw)
In-Reply-To: <20140828110556.GH26741@stefanha-thinkpad.redhat.com>

On Thu, Aug 28, 2014 at 12:05:56PM +0100, Stefan Hajnoczi wrote:
> On Thu, Aug 21, 2014 at 02:16:36PM +0100, Peter Maydell wrote:
> > On 21 August 2014 14:12, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > > On Thu, Aug 21, 2014 at 02:27:00PM +0200, Markus Armbruster wrote:
> > >> Should we have a variant of "make check-block" for testing other
> > >> (format, protocol) combinations?
> > >
> > > I don't think variants are useful.  If you need control, use ./check.
> > 
> > That seems pretty undiscoverable to me. I know about 'make check',
> > and 'make check-help' tells me about 'make check-block', but how
> > do I find out about 'check' ? I just had to bounce through the makefile
> > and a wrapper script to even figure out which directory it lives in,
> > and there's no help text or usage comments in it...
> 
> http://qemu-project.org/Documentation/QemuIoTests
> 
> Any suggestions for making it more discoverable?
> 

A couple of suggestions:

1.) Add a README file to the 'tests' directory

2.) Make the 'tests' directory more hierarchical.  It is not obvious
that 'qemu-iotests' (and the other tests) are something different than
the giant ball of .c files that is also in the tests directory. I
think it would be ideal to have the 'tests' directory contain 2 files
(Makefile, README), and then sub-directories.

  reply	other threads:[~2014-08-28 15:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21 12:27 [Qemu-devel] What tests should "make check-block" run? Markus Armbruster
2014-08-21 12:52 ` Paolo Bonzini
2014-08-21 13:00   ` Peter Crosthwaite
2014-08-22  5:01     ` Fam Zheng
2014-08-21 14:38   ` Kevin Wolf
2014-08-21 13:12 ` Stefan Hajnoczi
2014-08-21 13:16   ` Peter Maydell
2014-08-28 11:05     ` Stefan Hajnoczi
2014-08-28 15:22       ` Jeff Cody [this message]
2014-08-28 15:24       ` Markus Armbruster
2014-08-28 16:19         ` Peter Maydell
2014-08-29 20:05         ` Max Reitz
2014-09-01  7:55           ` Markus Armbruster
2014-08-28 23:50       ` Fam Zheng

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=20140828152231.GA11815@localhost.localdomain \
    --to=jcody@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).