Revision history for Test-Valgrind
+0.07 2008-09-30 13:35 UTC
+ + Chg : Now conforms to the Test::Builder framework.
+ + Fix : STDERR is longer eaten.
+ + Fix : Eat STDOUT or print it as diagnostics, but never let him go
+ through naked, as this may fiddle with the tests output.
+ + Fix : 'make test' without prior 'make'.
+
0.06 2008-09-09 22:10 UTC
+ Fix : Suppressions were installed in the wrong path. Thanks Marvin
Humphrey for reporting this.
Test::Valgrind - Test Perl code through valgrind.
VERSION
- Version 0.06
+ Version 0.07
SYNOPSIS
use Test::More;
You can't use this module to test code given by the "-e" command-line
switch.
- Results will most likely be better if your perl is built with debugging
+ Perl 5.8 is notorious for leaking like there's no tomorrow, so the
+ suppressions are very likely not to be very accurate on it. Anyhow,
+ results will most likely be better if your perl is built with debugging
enabled. Using the latest valgrind available will also help.
This module is not really secure. It's definitely not taint safe. That
shouldn't be a problem for test files.
- If your tests output to STDERR, everything will be eaten in the process.
- In particular, running this module against test files will obliterate
- their original test results.
+ What your tests output to STDOUT is eaten unless you pass the "diag"
+ option, in which case it will be reprinted as diagnostics. STDERR is
+ kept untouched.
DEPENDENCIES
Valgrind 3.1.0 (<http://valgrind.org>).
- Carp, POSIX (core modules since perl 5) and Test::More (since 5.6.2).
+ Carp, Fcntl, POSIX (core modules since perl 5) and Test::Builder (since
+ 5.6.2).
Perl::Destruct::Level.