History

Torsten Ruger c947c27a14 clean up booting many machine boot became obsolete or just neede parfait to boot actual linker functionality pending		2018-07-01 14:12:42 +03:00
..
source	adds arm testing of same files	2018-06-24 17:10:39 +03:00
helper.rb	adds arm testing of same files	2018-06-24 17:10:39 +03:00
README.md	adds arm testing of same files	2018-06-24 17:10:39 +03:00
test_arm.rb	clean up booting	2018-07-01 14:12:42 +03:00
test_interpreted.rb	generate mains test methods according to file name	2018-06-24 16:48:23 +03:00

README.md

Mains testing

Test methods by their output and exit codes (return, since it is the main).

There are only two tests here, one for interpreter, one for arm. Both run the same tests. The actual ruby code that is run is in the source dir. Test methods are generated, one for each source file.

File names follow [name,stdout,exitcode] joined by _ pattern. Stdout may be left blank, but exit code must be supplied.

Obviously the arm tests need an arm platform. This may be defined by ARM_HOST, eg for simulated ARM_HOST=localhost

Also port and user may be specified with ARM_PORT and ARM_USER , they default to 2222 and pi if left blank. SSH keys must be set up so no passwords are required (and the users private key may not be password protected)