Wednesday, December 12, 2012

Test Day 2012

Unit Testing isn't only just for testing your code, it is also for holding constant your external dependencies.  For example, your code uses an Open Source library.  Unit Testing is a perfect fit for documenting your assumptions/conditions on how the API currently works.  That way, when you upgrade to get the "improved caching" or some other whiz-bang feature, you can run your unit tests and verify that any under the covers kind of changes in the library hasn't broken your code.  Very slick.

And much better to find it when you upgrade your library, than weeks later when someone discovers a bug in your code when you don't have it fresh in your mind.

Participating in Test Day 2012.

blog comments powered by Disqus