History

Torsten Ruger cf05e7553a rework interpreter test framework remove lots of copy paste		2015-11-08 14:30:28 +02:00
..
bench	arm program to generate optimal devision code for constants	2014-05-15 16:53:47 +03:00
compiler	implement message pseudo variable (like self)	2015-11-08 13:55:38 +02:00
elf	remove passes and achieve the same by translating	2015-10-24 11:42:36 +03:00
interpreter	rework interpreter test framework	2015-11-08 14:30:28 +02:00
parfait	more layout tests, seeing class names on stdout	2015-11-08 00:55:37 +02:00
parfait_ruby	fixing indexes makes test work	2015-11-07 20:10:55 +02:00
register	fix padding	2015-11-04 10:34:03 +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	framework for parfait runtime testing	2015-11-07 17:37:41 +02: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