On 07/21/2017 04:34 AM, Stefan Hajnoczi 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 <chugh.ish...@research.iiit.ac.in> > Signed-off-by: Stefan Hajnoczi <stefa...@redhat.com> > ---
> +3. Assign groups to the test > + > +Add your test to the ./group file. This file is the index of tests and > assigns > +them to functional groups like "rw" for read-write tests. Most tests belong > to > +the "rw" and "auto" groups. "auto" means the test runs when ./check is > invoked > +without a -g argument. > + > +Consider adding your test to the "quick" group if it executes quickly (<1s). We have several tests going up to 5s (and I have a patch pending to remove two tests that took longer) - I think 1s is a bit on the short end for still classifying a test as quick. > +This group is run by "make check-block" and is often included as part of > build > +tests in continuous integration systems. It would still be nice to have 'make check' run 'make check-block'... but that's independent of this patch. > +Once you are happy with the test output it can be used as the golden master > +with "mv <test-number>.out.bad <test-number>.out". Rerun the test to verify > +that it passes. > + > +Congratulations, you've created a new test! Maybe a reminder to 'git add' the new files, then submit the patch? Better than what we have, so whether or not you make further tweaks according to my suggestions, Reviewed-by: Eric Blake <ebl...@redhat.com> -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature