History

Torsten Ruger f506f95cbf fixing basic and field access to return register as that is the new way, drop a layer, code to registers		2015-10-13 16:42:53 +03:00
..
bench	arm program to generate optimal devision code for constants	2014-05-15 16:53:47 +03:00
compiler	fixing basic and field access to return register	2015-10-13 16:42:53 +03:00
fragments	remove new_message instruction	2015-10-10 12:04:34 +03:00
interpreter	remove set optimization	2015-10-10 11:52:54 +03:00
parfait	fixed simple layout offset bug in layout	2015-10-13 14:46:07 +03:00
virtual	clean up more tests	2015-10-07 10:53:45 +03:00
helper.rb	move from new_object to normal new	2015-07-20 13:01:15 +03:00
README.md	went over the various readmes	2015-10-07 11:32:48 +03:00
test_all.rb	virtual tests back	2015-09-21 00:14:47 +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