History

Torsten Ruger 9c83423e50 bug hunting for class recreation		2017-01-17 21:25:58 +02:00
..
arm	put arm tests in arm module	2017-01-03 22:37:55 +02:00
bench	renames Typed to Vm	2017-01-14 19:28:44 +02:00
elf	fix tests for NameExpression split	2017-01-16 09:34:47 +02:00
lib	fix silly scope	2016-12-15 22:28:42 +02:00
melon	bug hunting for class recreation	2017-01-17 21:25:58 +02:00
register	move test helpers up, so they can be used in Melon too	2017-01-16 17:43:39 +02:00
vm	make method creation class methods in MethodCompiler	2017-01-17 21:23:58 +02:00
helper.rb	make method creation class methods in MethodCompiler	2017-01-17 21:23:58 +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	renames Typed to Vm	2017-01-14 19:28:44 +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