rubyx/test
Torsten Ruger 70d7e654c4 only check object file creation in efl
remote execution only per request
2018-06-25 00:39:13 +03:00
..
arm fix dynamic call 2018-06-25 00:19:43 +03:00
bench fix mod4 name 2018-04-19 10:00:55 +03:00
elf only check object file creation in efl 2018-06-25 00:39:13 +03:00
lib use modified opal logger 2018-05-20 14:45:48 +03:00
mains reusing ssh instance for arm 2018-06-24 17:44:02 +03:00
mom small maintanance 2018-06-16 21:01:15 +03:00
parfait small arm fixes etc 2018-06-06 00:53:41 +03:00
risc extract the ruby from mains tests 2018-06-24 11:56:10 +03:00
support fix the exit sequence 2018-06-19 19:52:06 +03:00
util small maintanance 2018-06-16 21:01:15 +03:00
vool assemble risc to it's position (not itself) 2018-05-17 09:49:01 +03:00
helper.rb integer was wrong padded§ length 2018-05-30 14:55:17 +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