bumblebee-status/runtests.sh

#!/bin/sh

echo "testing with $(python2 -V 2>&1)"
python2 $(which nosetests) -v --with-coverage --cover-erase tests/

if [ $? == 0 ]; then
	echo

	echo "testing with $(python3 -V 2>&1)"
	python3 $(which nosetests) -v --with-coverage --cover-erase tests/
fi
[tests] Added first module tests (for CPU) I finally really need to get started on testing. I've had too many releases in too short time intervals now, all because of small bugs/oversights. 2016-11-06 14:30:59 +01:00			`#!/bin/sh`

[core/engine] Add module loading logic Allow the engine to load modules from the bumblebee/modules/ directory. see #23 2016-12-04 11:09:10 +01:00			`echo "testing with $(python2 -V 2>&1)"`
[tests] Update runtests for Arch Linux compatibility 2017-12-29 14:52:07 +01:00			`python2 $(which nosetests) -v --with-coverage --cover-erase tests/`
[core/config] Add module aliases Allow the user to provide aliases when loading a module multiple times so that the modules can be differentiated (e.g. for passing parameters to a module). see #23 2016-12-03 20:54:57 +01:00
[core/engine] Add module loading logic Allow the engine to load modules from the bumblebee/modules/ directory. see #23 2016-12-04 11:09:10 +01:00			`if [ $? == 0 ]; then`
			`echo`
[core/config] Add module aliases Allow the user to provide aliases when loading a module multiple times so that the modules can be differentiated (e.g. for passing parameters to a module). see #23 2016-12-03 20:54:57 +01:00
[core/engine] Add module loading logic Allow the engine to load modules from the bumblebee/modules/ directory. see #23 2016-12-04 11:09:10 +01:00			`echo "testing with $(python3 -V 2>&1)"`
[tests] Update runtests for Arch Linux compatibility 2017-12-29 14:52:07 +01:00			`python3 $(which nosetests) -v --with-coverage --cover-erase tests/`
[core/engine] Add module loading logic Allow the engine to load modules from the bumblebee/modules/ directory. see #23 2016-12-04 11:09:10 +01:00			`fi`