ruby-x/rubyx
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
4f3a4387fc
rubyx/test
History
Torsten Ruger 4f3a4387fc renaming to_mom tests and improve guard
2017-09-04 21:00:29 +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 implements resolve_method on parfait type 2017-04-25 09:06:49 +03:00
risc 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 traces of salama 2017-08-29 18:38:51 +03:00
vool renaming to_mom tests and improve guard 2017-09-04 21:00:29 +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

README.md

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