History

Torsten Ruger bd171d091a fix tests for indexed messages and frames

index_length changes index a bit
but from now on changes to layouts should push the index automatically
just have to set the index while calling now

2015-10-27 16:05:50 +02:00

bench

arm program to generate optimal devision code for constants

2014-05-15 16:53:47 +03:00

compiler

fix tests for indexed messages and frames

2015-10-27 16:05:50 +02:00

elf

remove passes and achieve the same by translating

2015-10-24 11:42:36 +03:00

interpreter

removed blocks and moved to labels

2015-10-23 21:27:36 +03:00

parfait

fix tests for indexed messages and frames

2015-10-27 16:05:50 +02:00

minors

2015-10-26 17:23:35 +02:00

helper.rb

fold last of the virtual into register

2015-10-22 18:16:29 +03:00

README.md

went over the various readmes

2015-10-07 11:32:48 +03:00

test_all.rb

fold last of the virtual into register

2015-10-22 18:16:29 +03:00

test_runner.rb

update the reader rewrite and reflect name changes

2015-10-09 17:51:14 +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 / 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