diff options
author | Behdad Esfahbod <behdad@behdad.org> | 2008-05-15 18:50:55 -0400 |
---|---|---|
committer | Behdad Esfahbod <behdad@behdad.org> | 2008-05-15 19:27:17 -0400 |
commit | 142ba306047363af8343f29b2cf97c25919042e9 (patch) | |
tree | e1adab7b5a4691e625e8f00758fada09cebe793b /test/README | |
parent | 537ffa762833c990e4e4237f2dbae64c7e311662 (diff) |
[test/Makefile.am] Add 'make run' target
It runs tests under a tool specified tool. For example:
make run TOOL=gdb TESTS=user-font TARGETS=pdf
Diffstat (limited to 'test/README')
-rw-r--r-- | test/README | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/test/README b/test/README index a241d8a3..3b154e11 100644 --- a/test/README +++ b/test/README @@ -42,6 +42,25 @@ This will re-run the test suite, but only on tests that failed on the last run. So this is a much faster way of checking if changes actually fix bugs rather than running the entire test suite again. +Running tests under modified enviroments or tools +------------------------------------------------- +To run tests under a tool like gdb, one can use the run target and +the TOOL variable. For example: + + make run TOOL=gdb TARGETS=pdf TESTS=user-font + +If you want to run under valgrind, there is a specific target for that +that also sets a bunch of useful valgrind options. Try: + + make check-valgrind TESTS=user-font + +You can run tests under a modified environment you can use the ENV +make variable. However, that environment will also affect the libtool +wrapper of the tests. To only affect the actual test binaries, pass +such environment as TOOL: + + make run TOOL="LD_PRELOAD=/path/to/something.so" TEST=user-font + Getting the elusive zero failures --------------------------------- It's generally been very difficult to achieve a test run with zero |