[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: valgrind-tests.m4
From: |
Bruno Haible |
Subject: |
Re: valgrind-tests.m4 |
Date: |
Tue, 18 May 2010 11:22:34 +0200 |
User-agent: |
KMail/1.9.9 |
Ralf Wildenhues wrote:
> > However, in general, tests might be executable programs, or
> > they might be shell or other scripts. In the latter cases, putting
> > valgrind in TESTS_ENVIRONMENT would be at least a waste (you don't want
> > to check bash or perl).
Not only it's a waste. It also produces lots of stderr output that the
developer does not want to see.
Simon Josefsson wrote:
> It is a waste, but I've found that it is a small price to pay for
> valgrind test coverage. Most of my projects doesn't mix too many shell
> scripts with too many C files in the same test directory, too, so it has
> been a marginal problem for me.
In gettext, where most of the tests are shell scripts, for every program
'foo' to be tested:
- The TESTS_ENVIRONMENT defines a variable FOO="$(CHECKER) foo",
- The tests use : ${FOO=foo}
in order to provide a default value when the user is single-stepping
the test.
Bruno
- Re: valgrind-tests.m4, (continued)
- Re: valgrind-tests.m4, Ralf Wildenhues, 2010/05/17
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/17
- Re: valgrind-tests.m4, Ralf Wildenhues, 2010/05/17
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/18
- Re: valgrind-tests.m4, Ralf Wildenhues, 2010/05/19
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/19
- Re: valgrind-tests.m4, Ralf Wildenhues, 2010/05/20
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/20
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/20
- Re: valgrind-tests.m4,
Bruno Haible <=
- Re: valgrind-tests.m4, Simon Josefsson, 2010/05/18
- Re: valgrind-tests.m4, Bruno Haible, 2010/05/19
- Re: valgrind-tests.m4, Ralf Wildenhues, 2010/05/20
- Re: valgrind-tests.m4, Ben Pfaff, 2010/05/20
- Re: valgrind-tests.m4, Ralf Wildenhues, 2010/05/20