All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: lvm-devel@redhat.com
Subject: test/t1000-lvcreate-usage.sh: exercise lvcreate
Date: Mon, 17 Sep 2007 20:20:12 +0100	[thread overview]
Message-ID: <20070917192012.GN18444@agk.fab.redhat.com> (raw)
In-Reply-To: <873axdcpzg.fsf@rho.meyering.net>

On Mon, Sep 17, 2007 at 04:42:59PM +0200, Jim Meyering wrote:
> When I run the new test by itself, it does this:
>     # cd test && ./t1000-lvcreate-usage.sh
>     *   ok 1: set up temp files, loopback devices, PVs, and a VG
>     *   ok 2: lvcreate w/negative stripesize must fail
>     *   ok 3: lvcreate w/too-large stripesize must fail
>     *   ok 4: lvcreate w/single stripe succeeds with diagnostics to stdout
>     *   ok 5: lvcreate w/no stripe size succeeds with diagnostics to stdout
>     *   ok 6: lvcreate w/invalid number of stripes must fail
>     *   ok 7: lvcreate w/invalid stripe size must fail
>     * passed all 7 test(s)
 
Can you make that easier to parse?
Should every test have a reference number (perhaps derived from its
filename?) that is not going to change and appears on the output line?
Should each test belong to a defined category, e.g. 'lvcreate' above.
What role do the *s serve?  Would a wider range of characters make
the output more readable?
Can the version of the test also appear in the test logs along with
complete command output?  [I noticed a '>/dev/null' earlier that ought
to disappear:-) ]

'ok' with 'must fail' is misleading - try inverting the descriptions
e.g. 'rejects negative stripesizes'  (plural as I'd assume a range of
values are being tested each time)

Alasdair
-- 
agk at redhat.com



  reply	other threads:[~2007-09-17 19:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-17 14:42 test/t1000-lvcreate-usage.sh: exercise lvcreate Jim Meyering
2007-09-17 19:20 ` Alasdair G Kergon [this message]
2007-09-17 19:39   ` Jim Meyering
2007-09-17 19:49     ` Alasdair G Kergon

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=20070917192012.GN18444@agk.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=lvm-devel@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 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.