Now, I don’t subscribe to the philosophy of code your tests first, make them fail and then write your implementation. I prefer to write a method and then write the tests. It works better in my head. But just recently I’ve come across a pattern with my unit testing in dynamic languages where my unit integration tests fail first time around and this is happening allot.
To make matters worse it is the same problem each time. The results come up, a bunch of assertion fails. After looking at the results and the test code for a few minutes I move over to the “integration” code to see what is wrong, all looks good. So I start checking the individual objects and their methods and the problem becomes obvious. I’ve not written the method, hell, I’ve not even written the class yet.
This is what I miss the most in dynamic languages. I’ve gotten use to employing static testing that tells me; you know what, before you run your tests, try finishing the freaking program.
|
Ryan Boucher is a Software Inquisitor and is passionate about it. You can find a whole raft of articles and anecdotes about software testing and other topics he gets excited about. |
| Tags |
