mapnik/run_tests

#!/bin/sh

failures=0

PYTHON=${PYTHON:-python}

echo "*** Running visual tests..."
$PYTHON tests/visual_tests/test.py -q
failures=$((failures+$?))

echo "*** Running C++ tests..."
for FILE in tests/cpp_tests/*-bin; do 
	${FILE} -q -d .;
  failures=$((failures+$?))
done

echo

echo "*** Running python tests..."
$PYTHON tests/run_tests.py -q
failures=$((failures+$?))

exit $failures
Ensure proper exit code on any test failure. See #1611 Uses a shell script to run the tests. 2012-12-03 08:07:02 +00:00			`#!/bin/sh`

			`failures=0`

Allow user to specify a python executable.¬ ¬ Fall back on `python`. Unlike the solution in PR #2395 this¬ puts all the responsibility for selecting the right python in the¬ case that "python" is Python 3 on the user. I've followed the lead¬ of the Python documentation Makefile. See http://hg.python.org/cpython/file/340d48347295/Doc/README.txt http://hg.python.org/cpython/file/340d48347295/Doc/Makefile Intent is that if your `python` is Python 2 everything works as before and that is your `python` is Python 3 but you have a `python2` you can specify that instead.¬ 2014-09-03 21:57:27 +00:00			`PYTHON=${PYTHON:-python}`

Ensure proper exit code on any test failure. See #1611 Uses a shell script to run the tests. 2012-12-03 08:07:02 +00:00			`echo "*** Running visual tests..."`
Allow user to specify a python executable.¬ ¬ Fall back on `python`. Unlike the solution in PR #2395 this¬ puts all the responsibility for selecting the right python in the¬ case that "python" is Python 3 on the user. I've followed the lead¬ of the Python documentation Makefile. See http://hg.python.org/cpython/file/340d48347295/Doc/README.txt http://hg.python.org/cpython/file/340d48347295/Doc/Makefile Intent is that if your `python` is Python 2 everything works as before and that is your `python` is Python 3 but you have a `python2` you can specify that instead.¬ 2014-09-03 21:57:27 +00:00			`$PYTHON tests/visual_tests/test.py -q`
Ensure proper exit code on any test failure. See #1611 Uses a shell script to run the tests. 2012-12-03 08:07:02 +00:00			`failures=$((failures+$?))`

			`echo "*** Running C++ tests..."`
			`for FILE in tests/cpp_tests/*-bin; do`
more cpp test cleanup 2013-05-26 01:16:18 +00:00			`${FILE} -q -d .;`
Ensure proper exit code on any test failure. See #1611 Uses a shell script to run the tests. 2012-12-03 08:07:02 +00:00			`failures=$((failures+$?))`
			`done`

run in quiet mode 2013-05-25 00:22:28 +00:00			`echo`

Ensure proper exit code on any test failure. See #1611 Uses a shell script to run the tests. 2012-12-03 08:07:02 +00:00			`echo "*** Running python tests..."`
Allow user to specify a python executable.¬ ¬ Fall back on `python`. Unlike the solution in PR #2395 this¬ puts all the responsibility for selecting the right python in the¬ case that "python" is Python 3 on the user. I've followed the lead¬ of the Python documentation Makefile. See http://hg.python.org/cpython/file/340d48347295/Doc/README.txt http://hg.python.org/cpython/file/340d48347295/Doc/Makefile Intent is that if your `python` is Python 2 everything works as before and that is your `python` is Python 3 but you have a `python2` you can specify that instead.¬ 2014-09-03 21:57:27 +00:00			`$PYTHON tests/run_tests.py -q`
Ensure proper exit code on any test failure. See #1611 Uses a shell script to run the tests. 2012-12-03 08:07:02 +00:00			`failures=$((failures+$?))`

			`exit $failures`