[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TAP support in automake

From: Bob Friesenhahn
Subject: Re: TAP support in automake
Date: Sat, 31 Mar 2012 16:47:00 -0500 (CDT)
User-agent: Alpine 2.01 (GSO 1266 2009-07-14)

On Sat, 31 Mar 2012, Russ Allbery wrote:
This isn't the case if you have a sufficiently new version of the TAP
driver.  The TAP protocol allows the tests to not be numbered.  You lose
some robustness, since you then potentially don't know if a test was
skipped silently, but it's supported by C TAP Harness in the runtests.c
driver.  (The basic C TAP library doesn't support generating that style of
output, but that's because the library takes care of the counting for you,
so you don't need to keep track of test numbers.)

The numbers are useful. TAP is documented to support reporting the number of tests at the end of the test run rather than at the beginning.

Using your TAP test driver, and under the umbrella of Automake, how does one re-execute just one test in order to see the details of how it failed? The sample tests in your test harness expect that SOURCE and BUILD have already been set in the environment by Automake so just running via the suggested 'runtests -o' results in a failed test.

In Automake I do this like

  make TESTS=mytest

Using Perl's test driver I can execute one test like

  make TEST_VERBOSE=1 TEST_FILES=t/mytest.t test

How will the Automake 1.12 TAP driver handle this common special case?

Bob Friesenhahn
GraphicsMagick Maintainer,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]