[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [Qemu-devel] [PATCH] qemu-iotests: add a "how to" to ./
Re: [Qemu-block] [Qemu-devel] [PATCH] qemu-iotests: add a "how to" to ./README
Tue, 25 Jul 2017 16:20:52 +0100
On Mon, Jul 24, 2017 at 11:20:44AM +0100, Peter Maydell wrote:
> On 21 July 2017 at 10:34, Stefan Hajnoczi <address@hidden> wrote:
> > There is not much getting started documentation for qemu-iotests. This
> > patch explains how to create a new test and covers the overall testing
> > approach.
> > Cc: Ishani Chugh <address@hidden>
> > Signed-off-by: Stefan Hajnoczi <address@hidden>
> > ---
> > tests/qemu-iotests/README | 83
> > +++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 83 insertions(+)
> > diff --git a/tests/qemu-iotests/README b/tests/qemu-iotests/README
> > index 6079b40..8259b9f 100644
> > --- a/tests/qemu-iotests/README
> > +++ b/tests/qemu-iotests/README
> > @@ -14,8 +14,91 @@ Just run ./check to run all tests for the raw image
> > format, or ./check
> > -qcow2 to test the qcow2 image format. The output of ./check -h explains
> > additional options to test further image formats or I/O methods.
> > +* Testing approach
> > +
> > +Each test is an executable file (usually a bash script) that is run by the
> > +./check test harness. Standard out and standard error are captured to an
> > +output file. If the output file differs from the "golden master" output
> > file
> > +for the test then it fails.
> Should ./check be run from the source tree, or the build tree? The
> existing README text doesn't say and I don't think your additions
> do either.
It doesn't matter, both should work. The script detects both
possibilities and rejigs itself to compensate.
Description: PGP signature
Re: [Qemu-block] [Qemu-devel] [PATCH] qemu-iotests: add a "how to" to ./README, Eric Blake, 2017/07/24
Re: [Qemu-block] [PATCH] qemu-iotests: add a "how to" to ./README, Jeff Cody, 2017/07/26