ruby-x/rubyx
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

better test doc

Browse Source
This commit is contained in:
Torsten Ruger 2015-04-06 10:28:44 +03:00
parent 5b10f09ea1
commit 2a0dc7242a
1 changed files with 17 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
test/README.md
View File

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