unittesting 101

December 15th, 2005

Feasible for unit testing:

• simple methods whose output is easy to process (verify addNumbers(2, 2) gives 4)

Problematic scenarios:

• methods which output complex data (html, xml etc)
• methods which modify the state of the filesystem
• methods which make calls to outside binaries

:: random entries in this category ::

• whapple: evil you can't buy
• Not Invented Here illustrated (here)
• what is it about coding?

This entry was posted on Thursday, December 15th, 2005 at 3:21 am and is filed under technology. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

3 Responses to “unittesting 101”

1. erik says:

   December 15, 2005 at 3:23 pm

   *Sits on the sofa with a spoon in a bucket of Ben & Jerry’s with additional cookie crumbles all over his pyjama shirt as he watches Oprah*

   "So… How are you then?"

   Reply
2. numerodix says:

   December 15, 2005 at 4:22 pm

   That is a beautiful picture you painted, Oprah rocks. Well, sometimes.

   Reply