From: Jeff King <peff@peff.net>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: "Mårten Kongstad" <marten.kongstad@gmail.com>,
"Torsten Bögershausen" <tboegi@web.de>,
git@vger.kernel.org, gitster@pobox.com, johan@herland.net
Subject: Re: [PATCH v2] diff --shortstat --dirstat: remove duplicate output
Date: Wed, 4 Mar 2015 04:07:35 -0500 [thread overview]
Message-ID: <20150304090734.GA31245@peff.net> (raw)
In-Reply-To: <20150302020009.Horde.9sATpKnsrWQkGadaRTvxkA3@webmail.informatik.kit.edu>
On Mon, Mar 02, 2015 at 02:00:09AM +0100, SZEDER Gábor wrote:
> It's not just 'grep -c' but the 'test' checking its output as well.
>
> If something goes wrong and the line count doesn't match expectations
> 'test' fails silently leaving the developer clueless as to what went
> wrong.
>
> 'test_line_count', on the other hand, produces useful output in case
> of a failure:
>
> $ printf 'foo\nbar\n' >actual
> $ test_line_count = 1 actual
> test_line_count: line count for actual != 1
> foo
> bar
Since we have test_line_count, I think it makes sense to use it. But for
reference, I recently introduced the `verbose` function to test-lib.sh,
which lets you write:
$ verbose test 1 = 2
command failed: 'test' '1' '=' '2'
You can use it with any command that might fail without printing a
useful error message. The big downside is that it sees only the
arguments to the command, so if you write:
$ test "$(do_something)" = 123
you will only see:
command failed: 'test '456' '=' '123'
with no notion that $(do_something) was involved. So purpose-built
helpers like test_line_count will produce better output.
You may also be introduced in the "-x" option I recently introduced,
which can help with "quiet" failures. E.g.:
$ ./t0001-init.sh -x --verbose-only=15
[...]
ok 13 - GIT_DIR & GIT_WORK_TREE (2)
ok 14 - reinit
expecting success:
mkdir template-source &&
echo content >template-source/file &&
git init --template=../template-source template-custom &&
test_cmp template-source/file template-custom/.git/file
+ mkdir template-source
+ echo content
+ git init --template=../template-source template-custom
Initialized empty Git repository in /home/peff/compile/git/t/trash directory.t0001-init/template-custom/.git/
+ test_cmp template-source/file template-custom/.git/file
+ diff -u template-source/file template-custom/.git/file
ok 15 - init with --template
ok 16 - init with --template (blank)
(ok, it's not that interesting because the test didn't fail, but
hopefully you get the point).
Now I'll stop hijacking your thread to advertise random test-lib
features. :)
-Peff
prev parent reply other threads:[~2015-03-04 9:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 13:19 [PATCH] diff --shortstat --dirstat: remove duplicate output Mårten Kongstad
2015-02-28 14:21 ` Johan Herland
2015-03-01 3:54 ` Junio C Hamano
2015-03-01 7:39 ` [PATCH v2] " Mårten Kongstad
2015-03-01 10:25 ` Torsten Bögershausen
2015-03-01 14:23 ` Michael J Gruber
2015-03-01 16:01 ` Mårten Kongstad
2015-03-01 16:08 ` Michael J Gruber
2015-03-01 15:58 ` Mårten Kongstad
2015-03-02 1:00 ` SZEDER Gábor
2015-03-02 15:05 ` [PATCH v3] " Mårten Kongstad
2015-03-05 21:38 ` Junio C Hamano
2015-03-04 9:07 ` Jeff King [this message]
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=20150304090734.GA31245@peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
--cc=marten.kongstad@gmail.com \
--cc=szeder@ira.uka.de \
--cc=tboegi@web.de \
/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).