rubyx/test
2017-04-14 21:01:50 +03:00
..
arm remove all test_all 2017-04-13 17:00:56 +03:00
bench rename register to risc 2017-01-19 09:02:29 +02:00
elf remove all test_all 2017-04-13 17:00:56 +03:00
lib remove all test_all 2017-04-13 17:00:56 +03:00
mom remove all test_all 2017-04-13 17:00:56 +03:00
parfait update parfait message according to boot 2017-04-14 11:13:47 +03:00
risc remove all test_all 2017-04-13 17:00:56 +03:00
rubyx remove all test_all 2017-04-13 17:00:56 +03:00
support implements argument assignment 2017-04-13 14:14:43 +03:00
vm remove all test_all 2017-04-13 17:00:56 +03:00
vool introduce return_sequence instruction to mom 2017-04-14 21:01:50 +03:00
helper.rb more remote debugging 2017-04-14 14:38:23 +03:00
README.md add missing tests (that were not liked to the travis script) 2016-12-08 12:55:16 +02: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 salama, 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