I've been reading Better, Faster, Lighter Java and (like it many tech books) they always warn against a tool becoming a golden hammer. Which has got me wondering... is unit testing my golden hammer?
Any (programming) task I have, I try my best to write a test for it. Is this a bad thing? I never thought so. I write tests for resource files, to test config files, anything that I can write a test for, I do. I've just been thinking about this because someone was surprised that I was writing tests to test my Commons Validator configuration. Strange? Maybe. Documenting how the app is supposed to work? I think so.
No comments:
Post a Comment