From 2a0dc7242afb6f61c91118ba7c3018fdb0168f53 Mon Sep 17 00:00:00 2001 From: Torsten Ruger Date: Mon, 6 Apr 2015 10:28:44 +0300 Subject: [PATCH] better test doc --- test/README.md | 22 +++++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/test/README.md b/test/README.md index e1155068..aca94758 100644 --- a/test/README.md +++ b/test/README.md @@ -6,13 +6,25 @@ Good tests exists in the parts where functionality is clear: Parsing and binary 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. -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. - 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. -## Commands +### All -bundle exec rake test +'''' + 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 :-)