History

Torsten Ruger 83ab197d03 fix and test vool return statement		2017-04-04 10:42:20 +03:00
..
arm	rename register to risc	2017-01-19 09:02:29 +02:00
bench	rename register to risc	2017-01-19 09:02:29 +02:00
elf	rename register to risc	2017-01-19 09:02:29 +02:00
lib	fix silly scope	2016-12-15 22:28:42 +02:00
parfait	order test requires	2017-04-02 22:42:51 +03:00
risc	order test requires	2017-04-02 22:42:51 +03:00
rubyx	order test requires	2017-04-02 22:42:51 +03:00
vm	rename register to risc	2017-01-19 09:02:29 +02:00
vool	fix and test vool return statement	2017-04-04 10:42:20 +03:00
helper.rb	rename register to risc	2017-01-19 09:02:29 +02: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	order test requires	2017-04-02 22:42:51 +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 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