rubyx/test
Torsten Ruger 22b1fea587 use rubyc_compiler as instance
not as before class methods
so we can carry the state around
2018-07-01 11:59:07 +03:00
..
arm hoist parfait boot out of the machine boot 2018-06-30 00:39:23 +03:00
bench fix mod4 name 2018-04-19 10:00:55 +03:00
elf hoist parfait boot out of the machine boot 2018-06-30 00:39:23 +03:00
lib use modified opal logger 2018-05-20 14:45:48 +03:00
mains fix remaining tests 2018-06-29 22:56:49 +03:00
mom hoist parfait boot out of the machine boot 2018-06-30 00:39:23 +03:00
parfait hoist parfait boot out of the machine boot 2018-06-30 00:39:23 +03:00
risc remove translation 2018-07-01 11:58:06 +03:00
rubyx use rubyc_compiler as instance 2018-07-01 11:59:07 +03:00
support use rubyc_compiler as instance 2018-07-01 11:59:07 +03:00
util small maintanance 2018-06-16 21:01:15 +03:00
vool start on class compiler 2018-06-30 19:20:17 +03:00
helper.rb hoist parfait boot out of the machine boot 2018-06-30 00:39: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