I totally understand the point that was trying to get across, but the code picked that was demonstrated I think was actually not too difficult to test... There is much harder code to test, when you get strange states and global state that you can't override... The approach demonstrated worked well, but in my experience I think (in my opinion of course) sometimes you just HAVE to refactor to make things more "testable".
There's not much to say. Michelangelo's presentations on testing are always spot on in terms of content and delivery. Testing is important and it should always be an integral part of development.
Comments
Comments are closed.
Interesting to see how straight-forward it can be to create unit tests for legacy code. Rats!;-)
I totally understand the point that was trying to get across, but the code picked that was demonstrated I think was actually not too difficult to test... There is much harder code to test, when you get strange states and global state that you can't override... The approach demonstrated worked well, but in my experience I think (in my opinion of course) sometimes you just HAVE to refactor to make things more "testable".
There's not much to say. Michelangelo's presentations on testing are always spot on in terms of content and delivery. Testing is important and it should always be an integral part of development.