rubyx/test
Torsten Ruger 5f628744d6 more test working
operator wip
2015-09-20 16:52:26 +03:00
..
bench arm program to generate optimal devision code for constants 2014-05-15 16:53:47 +03:00
compiler temporarily disabling test that haven't been fixed yet 2015-09-19 22:24:57 +03:00
fragments more test working 2015-09-20 16:52:26 +03:00
interpreter switching to ast::processor 2015-09-19 18:56:18 +03:00
parfait small rename and new test for layout 2015-08-08 18:08:47 +03:00
virtual add guard 2015-08-08 18:08:15 +03:00
helper.rb move from new_object to normal new 2015-07-20 13:01:15 +03:00
README.md move sof to own repo 2015-05-03 20:38:13 +03:00
test_all.rb temporarily disabling test that haven't been fixed yet 2015-09-19 22:24:57 +03:00
test_runner.rb work on ObjectWriter 2015-05-16 12:53:10 +03:00

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 :-)