History

Torsten Ruger 3bdba119c8 fix the list after object fixes start index at 1, but don’t overwrite layout, so add one		2015-05-17 14:56:06 +03:00
..
arm	fix test	2015-03-28 21:12:03 +02:00
bench	arm program to generate optimal devision code for constants	2014-05-15 16:53:47 +03:00
fragments	rename old layout()	2015-05-17 14:41:18 +03:00
parfait	fix the list after object fixes	2015-05-17 14:56:06 +03:00
virtual	improve boot	2015-05-16 20:16:49 +03:00
graph_helper.rb	get thnads tests to work	2014-04-24 15:53:48 +03:00
helper.rb	move object equality here	2014-09-16 16:06:11 +03:00
README.md	move sof to own repo	2015-05-03 20:38:13 +03:00
test_all.rb	fixes parfaits hash by implementing array	2015-05-12 18:52:01 +03:00
test_runner.rb	work on ObjectWriter	2015-05-16 12:53:10 +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 ''''

vm

As this is all quite new, i tend to test only when i know that the functionality will stay that way. Otherwise it's just too much effort to rewrite and rewrite the tests.

There used to be better tests, but rewrites bring fluctuation, so poke around and make suggestion :-)