History

Torsten Ruger ed6fd91c4e add missing tests (that were not liked to the travis script)		2016-12-08 12:55:16 +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 missing tests (that were not liked to the travis script)	2016-12-08 12:55:16 +02:00
helper.rb	fix codeclimate braking changes	2016-12-06 15:22:22 +02:00
README.md	add missing tests (that were not liked to the travis script)	2016-12-08 12:55:16 +02:00
test_all.rb	add missing tests (that were not liked to the travis script)	2016-12-08 12:55:16 +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 as the framework, 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