rubyx/test
Torsten Ruger a2e7d7c469 give interpreter a clock and pc
where the pc, like in cpu’s is the memory position.
That is what the interpreter works on.
But for humans, the clock is a simpler way to count where the program
is at, no. of instructions executed
2018-05-23 18:05:22 +03:00
..
arm make the interpreter platform 2018-05-17 09:31:36 +03:00
bench fix mod4 name 2018-04-19 10:00:55 +03:00
elf change to position objects complete 2018-05-05 20:25:10 +03:00
lib use modified opal logger 2018-05-20 14:45:48 +03:00
mom assemble risc to it's position (not itself) 2018-05-17 09:49:01 +03:00
parfait another +1 bug 2018-05-15 16:25:55 +03:00
risc give interpreter a clock and pc 2018-05-23 18:05:22 +03:00
support use positions in interpreter 2018-05-20 15:52:13 +03:00
vool assemble risc to it's position (not itself) 2018-05-17 09:49:01 +03:00
helper.rb more remote debugging 2017-04-14 14:38:23 +03:00
README.md remove traces of salama 2017-08-29 18:38:51 +03:00
test_all.rb restrict tests to test dir 2017-04-14 20:37:47 +03:00

Testing

Testing is off course great, and well practised in the ruby community. Good tests exists in the parts where functionality is clear: Parsing and binary generation.

But it is difficult to write tests when you don't know what the functionality is. Also TDD does not really help as it assumes you know what you're doing.

I used minitest as the framework, just because it is lighter and thus when the time comes to move to rubyx, less work.

All

'''' ruby test/test_all.rb ''''

Parfait

Well, test Parfait. Not perfect, but growing as bugs appear. Basics are ok though.

Compiler

Different kinds of quite minimal tests that ensure we can go from parsed to code.

Fragments

Much more elaborate tests of the compling functionality. All code constructs and their output in terms of instructions are tested.

vm

Mostly tests about the Parfait compatibility layer and padding (for assmenbly). Slightly bad name ... wip