On 01/27/2011 05:20 PM, Daily, Jeff A wrote:
> In a nutshell, I've written a drop-in replacement of another tool and would
> like to test that it functions identical to the original. All you need to
> know about these tools is that they take as input one or more binary files
> and produce a sin
[adding automake]
On 01/28/2011 04:38 AM, Bruno Haible wrote:
> Hi,
>
> Can you use $(FOO-BAR) in Makefile? It's not portable in POSIX [1]
Then let's get that addressed in POSIX! We're already in the middle of
getting POSIX to support ${var${v}} nested variable expansions, on the
same arguments
Hi,
On Fri, 28 Jan 2011, Eric Blake wrote:
> On 01/27/2011 05:20 PM, Daily, Jeff A wrote:
> > In a nutshell, I've written a drop-in replacement of another tool and would
> > like to test that it functions identical to the original. All you need to
> > know about these tools is that they take a
On 01/28/2011 10:49 AM, Joel E. Denny wrote:
>>> AT_SETUP([testing $file, no arguments])
>>> for file in $datadir/*
>>> do
>>> AS_IF([bad $file], [continue])
>>> AT_CHECK([replacement $file -o replacement.out])
>>> AT_CHECK([original $file -o original.out])
>>> AT_CHECK([pgcmp repla
On Fri, 28 Jan 2011, Eric Blake wrote:
> Unfortunately correct - if you want multiple tests (that is, where you
> can run a subset of the testsuite using just testsuite arguments, rather
> than hacking the 'bad' script filter in that initial AS_IF of the
> example above), then you must surround AT
* Joel E. Denny wrote on Fri, Jan 28, 2011 at 08:06:38PM CET:
> A way to get the best of both worlds might be to permit shell functions
> containing AT_CHECK to be defined outside of AT_SETUP. I believe that is
> not possible with autotest now, and I have no idea if it's feasible to
> implement
I want to dump some environment variables near the top of my tests suite since
these variables affect my tests. In my local.at file I have:
AT_INIT
AS_ECHO(["tests use seq $NP_START $NP_INC $NP_STOP"])
But it doesn't make it into my suite script at all. I would like for the echo
to go to both
On Fri, 28 Jan 2011, Ralf Wildenhues wrote:
> * Joel E. Denny wrote on Fri, Jan 28, 2011 at 08:06:38PM CET:
> > A way to get the best of both worlds might be to permit shell functions
> > containing AT_CHECK to be defined outside of AT_SETUP. I believe that is
> > not possible with autotest now
* Joel E. Denny wrote on Fri, Jan 28, 2011 at 08:31:05PM CET:
> On Fri, 28 Jan 2011, Ralf Wildenhues wrote:
> > * Joel E. Denny wrote on Fri, Jan 28, 2011 at 08:06:38PM CET:
> > > A way to get the best of both worlds might be to permit shell functions
> > > containing AT_CHECK to be defined outsid
