fonttools/run-tests.sh

#!/bin/sh

# exit if any subcommand return non-zero status
set -e

# Choose python version
if test "x$1" = x-3; then
	PYTHON=python3
	shift
elif test "x$1" = x-2; then
	PYTHON=python2
	shift
fi
test "x$PYTHON" = x && PYTHON=python

# Find tests
FILTERS=
for arg in "$@"; do
	test "x$FILTERS" != x && FILTERS="$FILTERS or "
	FILTERS="$FILTERS$arg"
done

# Run tests
if [ -z "$FILTERS" ]; then
	$PYTHON -m pytest
else
	$PYTHON -m pytest -k "$FILTERS"
fi
Fix checks; add run-tests.sh 2015-03-03 09:57:41 -08:00			`#!/bin/sh`
Add -2 and -3 to run-tests.sh to choose Python 2 / 3 2015-04-15 17:41:12 -07:00
run-test.sh: exit immediately if any subcommands return non-zero value 2015-12-11 16:10:51 +00:00			`# exit if any subcommand return non-zero status`
			`set -e`

Add -2 and -3 to run-tests.sh to choose Python 2 / 3 2015-04-15 17:41:12 -07:00			`# Choose python version`
			`if test "x$1" = x-3; then`
			`PYTHON=python3`
			`shift`
			`elif test "x$1" = x-2; then`
			`PYTHON=python2`
			`shift`
			`fi`
			`test "x$PYTHON" = x && PYTHON=python`

			`# Find tests`
[run-test.sh] use pytest to collect tests This way test discovery will work not only with the current unittest and doctest modules, but also with pytest's own kind of tests. When run with no argument, the shell script will call the py.test command, which will scan the whole Lib/fontTools directory for all relevant tests. If args are provided, tests are filtered if any of the substrings specified match. The filtering works not only on the modules' file names (as the previous grep approach), but also on the names of the test functions, classes and methods. Pretty cool, huh? We can still specify whether to run pytest with python -2 or -3 (provided pytest is installed on both Python versions). And we don't need to print the python version any more as pytest does it for us. Finally, there's no need to export PYTHONPATH -- pytest takes care of that too! 2016-02-06 21:53:01 +00:00			`FILTERS=`
Try fixing the build 2015-04-19 11:53:35 -07:00			`for arg in "$@"; do`
[run-test.sh] use pytest to collect tests This way test discovery will work not only with the current unittest and doctest modules, but also with pytest's own kind of tests. When run with no argument, the shell script will call the py.test command, which will scan the whole Lib/fontTools directory for all relevant tests. If args are provided, tests are filtered if any of the substrings specified match. The filtering works not only on the modules' file names (as the previous grep approach), but also on the names of the test functions, classes and methods. Pretty cool, huh? We can still specify whether to run pytest with python -2 or -3 (provided pytest is installed on both Python versions). And we don't need to print the python version any more as pytest does it for us. Finally, there's no need to export PYTHONPATH -- pytest takes care of that too! 2016-02-06 21:53:01 +00:00			`test "x$FILTERS" != x && FILTERS="$FILTERS or "`
			`FILTERS="$FILTERS$arg"`
Process all arguments to run-tests.sh as filters 2015-04-19 04:56:08 -07:00			`done`

[run-test.sh] use pytest to collect tests This way test discovery will work not only with the current unittest and doctest modules, but also with pytest's own kind of tests. When run with no argument, the shell script will call the py.test command, which will scan the whole Lib/fontTools directory for all relevant tests. If args are provided, tests are filtered if any of the substrings specified match. The filtering works not only on the modules' file names (as the previous grep approach), but also on the names of the test functions, classes and methods. Pretty cool, huh? We can still specify whether to run pytest with python -2 or -3 (provided pytest is installed on both Python versions). And we don't need to print the python version any more as pytest does it for us. Finally, there's no need to export PYTHONPATH -- pytest takes care of that too! 2016-02-06 21:53:01 +00:00			`# Run tests`
			`if [ -z "$FILTERS" ]; then`
			`$PYTHON -m pytest`
Report failing modules 2015-04-21 11:06:56 -07:00			`else`
[run-test.sh] use pytest to collect tests This way test discovery will work not only with the current unittest and doctest modules, but also with pytest's own kind of tests. When run with no argument, the shell script will call the py.test command, which will scan the whole Lib/fontTools directory for all relevant tests. If args are provided, tests are filtered if any of the substrings specified match. The filtering works not only on the modules' file names (as the previous grep approach), but also on the names of the test functions, classes and methods. Pretty cool, huh? We can still specify whether to run pytest with python -2 or -3 (provided pytest is installed on both Python versions). And we don't need to print the python version any more as pytest does it for us. Finally, there's no need to export PYTHONPATH -- pytest takes care of that too! 2016-02-06 21:53:01 +00:00			`$PYTHON -m pytest -k "$FILTERS"`
Really fix test runner this time Still doesn't work as we don't return failure from the Python fails if doctests fail. But the test runner script is correct now. 2015-03-03 10:39:55 -08:00			`fi`