From 5c8b5233fbadc8963cef28d851599bf4c34d271a Mon Sep 17 00:00:00 2001
From: Simon Ruderich <simon@ruderich.org>
Date: Fri, 7 Jun 2013 01:17:42 +0200
Subject: [PATCH] tests: Run tests under valgrind if it's available.

---
 tests/lib.sh | 2 +-
 tests/run.sh | 7 +++++++
 2 files changed, 8 insertions(+), 1 deletion(-)

diff --git a/tests/lib.sh b/tests/lib.sh
index 53a2ea4..3e29a55 100644
--- a/tests/lib.sh
+++ b/tests/lib.sh
@@ -74,7 +74,7 @@ run_test() {
             export COLORED_STDERR_FORCE_WRITE
         fi
 
-        "$@" "$testcase" > output 2>&1
+        $valgrind_cmd "$@" "$testcase" > output 2>&1
     )
 
     diff -u "$expected" output \
diff --git a/tests/run.sh b/tests/run.sh
index abd0e28..186b24b 100755
--- a/tests/run.sh
+++ b/tests/run.sh
@@ -25,6 +25,13 @@ test "x$srcdir" = x && srcdir=.
 . "$srcdir/lib.sh"
 
 
+# Use valgrind to run the tests if it's available.
+valgrind_cmd=
+if type valgrind >/dev/null 2>&1; then
+    valgrind_cmd='valgrind --quiet --error-exitcode=1'
+fi
+
+
 # Make sure we don't write to non-ttys by default.
 force_write=
 test_script example-noforce.sh
-- 
2.43.2