lms-video/Gem/tests
Santi Noreña e85d191b46 - Reestructuración de ficheros y directorios general
- merge v0.01 --> Añadido fileselector
- Añadidas fuentes de Gem y Pure Data
- pix2jpg incluído en Gem. Archivos de construcción de Gem modificados.
- Añadido fichero ompiling.txt con instrucciones de compilación
2013-02-04 18:00:17 +01:00
..
all - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
data - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
gemframebuffer - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
pix_2grey - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
pix_data - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
crashers.txt - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
README.txt - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
runcrashtests_gui.pd - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
runcrashtests_nogui.pd - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
runtests.pd - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
runtests.sh - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
runtests_nogui.pd - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
testcrashunit.pd - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00
testunit.pd - Reestructuración de ficheros y directorios general 2013-02-04 18:00:17 +01:00

regression tests for Gem


tests are pd-patches living in subdirectories from here

naming conventions:
 subdirectories: 
	named after the (main) object to be tested
	e.g. gemframebuffer/ tests problems in [gemframebuffer]

 tests:
	tests starting with "crash_" are supposed to crash Pd
	tests starting with "fail_" are supposed to fail the unit-test
	all other tests are supposed to survive and pass the test


unit-tests:
 starting the test:
	each unit-test get's called with a uniq-ID as first argument
	it is supposed to create a receiver using this uniq-ID as follows
		[r $1-start]
	when a bang is received on this label, the test must start
 evaluating the test:
	each unit-test is supposed to create a sender using the uniq-ID:
		[s $1-result]
	the unit test can send 3 results to this label:
	 0: the test has failed
	 1: the test has passed
	-1: wait, not yet finished!
 running the test:
	when a "bang" is received at "$1-start", the test has to start and
	_immediately_ return one of the 3 results to "$1-result"
	if the test fails to immediately return a result, it is considered
	as FAILED and the test-run is stopped (the unit-test is deleted!)
	if the test needs some time to evaluate, it MUST send "-1" as a result
	in which case the test-engine is paused and waits for a proper result
	(0 or 1) in order to continue