automake-ng
[Top][All Lists]
Advanced

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

Re: [Automake-NG] [PATCH 20/17] [ng] news: update w.r.t. recent changes


From: Bob Friesenhahn
Subject: Re: [Automake-NG] [PATCH 20/17] [ng] news: update w.r.t. recent changes in testsuite harnesses (TESTS based)
Date: Tue, 29 May 2012 14:15:36 -0500 (CDT)
User-agent: Alpine 2.01 (GSO 1266 2009-07-14)

On Tue, 29 May 2012, Akim Demaille wrote:


Le 23 mai 2012 à 11:34, Stefano Lattarini a écrit :

+  This is not a big deal in practice, since as of today, all the real
+  world packages out there actually use 'test-driver' for most (if not
+  all) of their tests (the introduction of TAP support in mainstream
+  automake being too recent for those packages to have had time to phase
+  out their protocol-less tests, assuming they wanted to -- which is
+  usually not the case either).

Actually I don't even know what benefit there is from using
this "standard" (even though I google'd, and browsed the
Automake documentation (btw, there is no index for TAP)).

As described to me, it is to solve the problem that parallel-tests mode (really tests with per-test log files) is incapable of supporting large test suites on systems with command-line length restrictions. ;-)

I see some benefits from TAP but I also see useful features missing from it. A weakness of TAP is that the test itself is expected to know when the test is expected to fail. With Automake tests, this was configured externally.

Bob
--
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

reply via email to

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