History

Torsten Ruger 707c180cab add go results, just cause I'm learning it		2015-11-27 19:54:43 +02:00
..
bench	add go results, just cause I'm learning it	2015-11-27 19:54:43 +02:00
elf	fix the putstring sys call indexing	2015-11-15 22:03:06 +02:00
register	take the benchmark tests out from the soml	2015-11-21 14:33:52 +02:00
soml	moved all the ruby benches out of the tests	2015-11-21 16:33:43 +02:00
helper.rb	reinstate word creation and use for strings	2015-11-08 23:58:35 +02:00
README.md	went over the various readmes	2015-10-07 11:32:48 +03:00
test_all.rb	move parfait tests to some	2015-11-18 12:14:31 +02:00
test_runner.rb	better error reporting for parser	2015-11-19 10:10:13 +02: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 / test-unit as the framewok, 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