From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Mon, 14 Jun 2010 22:29:29 GMT
Subject: Re: [PATCH v2 1/3] Make test-lib.sh emit valid TAP format
Message-ID: <AANLkTik4Zxh5cKUEn1_yoNGKvNSudILvEVEAqeeElmB0@mail.gmail.com>
In-Reply-To: <m31vc9p93t.fsf@localhost.localdomain>

On Mon, Jun 14, 2010 at 22:01, Jakub Narebski <jnareb@gmail.com> wrote:
> Ævar Arnfjörð Bjarmason  <avarab@gmail.com> writes:
>
>> TAP, the Test Anything Protocol, is a simple text-based interface
>> between testing modules in a test harness. test-lib.sh's output was
>> already very close to being valid TAP. This change brings it all the
>> way there. Before:
>>
>>    $ ./t0005-signals.sh
>>    *   ok 1: sigchain works
>>    * passed all 1 test(s)
>>
>> And after:
>>
>>    $ ./t0005-signals.sh
>>    ok 1 - sigchain works
>>    # passed all 1 test(s)
>>    1..1
>
> How failing test looks like before and after the change?
>
> How test_expect_failure, i.e. known breakage (TODO test) looks like
> (both in known broken, and in accidentally fixed version) before and
> after the change?
>
> How does '--verbose' and '--debug' output looks like before and after
> the change?

I'll submit a version with an updated commit message. The gist of it:

 * It's now ok/not ok instead of ok/failed
 * --debug and --verbose work just like before
 * Other things look like before, but may be changed to make TAP like
it (e.g. prefixing comments with #)