History

Torsten Ruger 2741f35380 add a each_pair to indexed and use in types		2016-12-07 23:35:51 +02:00
..
bench	fix benches interfering with testing	2015-11-30 16:09:55 +02:00
elf	fix the putstring sys call indexing	2015-11-15 22:03:06 +02:00
lib	fix rename	2016-12-06 16:45:16 +02:00
melon	fix docs for rename	2016-02-25 12:03:11 -08:00
register	move tests to equivalent place	2016-12-06 16:54:26 +02:00
typed	add a each_pair to indexed and use in types	2016-12-07 23:35:51 +02:00
helper.rb	fix codeclimate braking changes	2016-12-06 15:22:22 +02:00
README.md	went over the various readmes	2015-10-07 11:32:48 +03:00
test_all.rb	Move type tests around	2016-12-06 16:58:19 +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