Unit testing *cannot* prove correctness by itself, try this for a thought experiment:
- You have a `divide` method. - You test it against all possible input: integers, floating points, zeros, negative numbers, very big numbers, very small numbers - You make sure you have 100% code coverage, that your test is ensuring everything works as expected - You expose this method as part of your API Then - Someone calls it, passing a String as an argument On 30 July 2012 10:33, Dale Wijnand <[email protected]> wrote: > On Monday, July 30, 2012 12:54:34 AM UTC+2, rakesh mailgroups wrote: >> >> "you might find that compiler help isn't all that important in the end" >> > > There is a research that seems to prove that "unit testing isn't enough, > you need static typing", which is very interesting. Here: > > http://evanfarrer.blogspot.it/2012/06/unit-testing-isnt-enough-you-need.html > > Dale > > > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
