History

Torsten Rüger 12b29285d7 Lots of preloading for tests so many relied (implicitly( on some builtin function after all can't do much in ruby without calling Now all those dependencies are explicit Small risc changes come because the macro version has a return label and unreachable label		2019-09-13 14:07:12 +03:00
..
source	fix interpreter to output symbols	2019-09-08 15:31:03 +03:00
helper.rb	adds arm testing of same files	2018-06-24 17:10:39 +03:00
README.md	Successfully interpret class methods	2019-02-27 09:48:21 +02:00
test_arm.rb	update gems, remove ssh	2019-09-08 13:44:51 +03:00
test_interpreted.rb	Lots of preloading for tests	2019-09-13 14:07:12 +03:00
test_new.rb	Lots of preloading for tests	2019-09-13 14:07:12 +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 (lus one, see below), 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.

Files

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

Arm

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)

Developing

Since the Framework always runs all tests, it is a little cumbersome for developing a single new test. Since all get run and it is slow.

To develop the next test, one can edit test_new.rb . Once it runs on the interpreter, move the changes to a source file and revert test_new changes.