History

Torsten Ruger bc22c40101 Get Byte interpreter test		2016-12-15 22:15:58 +02:00
..
arm	memory instruction refactor (small)	2016-12-14 21:05:24 +02:00
bench	remove references to soml	2016-12-11 12:55:03 +02:00
elf	minor	2016-12-15 18:08:55 +02:00
lib	complete log tests	2016-12-15 22:14:24 +02:00
melon	small collector change	2016-12-08 15:19:37 +02:00
register	Get Byte interpreter test	2016-12-15 22:15:58 +02:00
typed	more class tests	2016-12-15 22:15:40 +02:00
helper.rb	exclude test from coverage (duh)	2016-12-10 18:59:24 +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	folded salama-arm in	2016-12-14 13:43: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