History

Torsten Ruger 2a0dc7242a better test doc		2015-04-06 10:28:44 +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	get some old builtin code backonline and improve imports	2014-09-09 18:03:13 +03:00
parfait	fix parfait test	2014-09-04 14:22:28 +03:00
virtual	update read me	2015-03-15 11:58:17 +00: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	better test doc	2015-04-06 10:28:44 +03:00
sof.rb	short hash, inline like for array. with curly braces off course	2014-08-27 14:46:34 +03:00
test_all.rb	fix parfait test	2014-09-04 14:22:28 +03:00
test_runner.rb	more renaming ripples	2014-08-22 18:00:23 +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 ''''

sof

'''' ruby test/test_sof.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 :-)