mapnik/run_tests

#!/bin/bash

failures=0

source ./localize.sh
PYTHON=${PYTHON:-python}

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

echo "*** Running C++ tests..."
./tests/cpp_tests/run
failures=$((failures+$?))
echo

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

exit $failures
use bash in all shell scripts 2013-11-22 22:46:05 +01:00			`#!/bin/bash`
Ensure proper exit code on any test failure. See #1611 Uses a shell script to run the tests. 2012-12-03 09:07:02 +01:00
			`failures=0`

rework tests: always run locally 2013-11-22 21:01:02 +01:00			`source ./localize.sh`
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.¬ Conflicts: run_tests 2014-09-03 23:57:27 +02:00			`PYTHON=${PYTHON:-python}`
rework tests: always run locally 2013-11-22 21:01:02 +01:00
Ensure proper exit code on any test failure. See #1611 Uses a shell script to run the tests. 2012-12-03 09:07:02 +01: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.¬ Conflicts: run_tests 2014-09-03 23:57:27 +02: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 09:07:02 +01:00			`failures=$((failures+$?))`

			`echo "*** Running C++ tests..."`
rework tests: always run locally 2013-11-22 21:01:02 +01:00			`./tests/cpp_tests/run`
			`failures=$((failures+$?))`
run in quiet mode 2013-05-25 02:22:28 +02:00			`echo`

Ensure proper exit code on any test failure. See #1611 Uses a shell script to run the tests. 2012-12-03 09:07:02 +01: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.¬ Conflicts: run_tests 2014-09-03 23:57:27 +02: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 09:07:02 +01:00			`failures=$((failures+$?))`

			`exit $failures`