Only Java developers omit tests like in this project: https://github.com/projectwonder/wonder -- 2800 class files and just 56 test-units. Usually here, commits that fix bugs do not contribute to the test suite -- typically perl projects do a better job!
for example, evil are those that test only the success
other evil tests are those where you directly input the initial data, then test a class or a method or a script on them: those break when the applications changes and the input data is changed, but you never find out and enjoy the rows of OKs, or you have to fix them all the time
...but good perl developers always test well :-)
ReplyDeleteOnly Java developers omit tests like in this project: https://github.com/projectwonder/wonder -- 2800 class files and just 56 test-units. Usually here, commits that fix bugs do not contribute to the test suite -- typically perl projects do a better job!
#!perl
ReplyDeleteuse Test::Simple tests => 1;
ok(1);
I'm sorry but HUH? how are bad tests worse than no tests? and what is a bad test? (maybe I just don't know how to write them)
ReplyDeletefor example, evil are those that test only the success
ReplyDeleteother evil tests are those where you directly input the initial data, then test a class or a method or a script on them: those break when the applications changes and the input data is changed, but you never find out and enjoy the rows of OKs, or you have to fix them all the time