2018-06-24 16:10:39 +02:00
|
|
|
# Mains testing
|
2018-04-24 19:12:49 +02:00
|
|
|
|
2019-02-27 08:48:21 +01:00
|
|
|
Test methods by their output and exit codes (return, since it is the main).
|
2018-04-24 19:12:49 +02:00
|
|
|
|
2019-02-27 08:48:21 +01:00
|
|
|
There are only two tests here (lus one, see below), one for interpreter, one for arm.
|
2018-06-24 16:10:39 +02:00
|
|
|
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.
|
|
|
|
|
|
2019-02-27 08:48:21 +01:00
|
|
|
## Files
|
|
|
|
|
|
2018-06-24 16:10:39 +02:00
|
|
|
File names follow [name,stdout,exitcode] joined by _ pattern. Stdout may be left blank,
|
|
|
|
|
but exit code must be supplied.
|
|
|
|
|
|
2019-02-27 08:48:21 +01:00
|
|
|
## Arm
|
|
|
|
|
|
2018-06-24 16:10:39 +02:00
|
|
|
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)
|
2019-02-27 08:48:21 +01:00
|
|
|
|
|
|
|
|
## 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.
|
