Specifications are great, tests or so so, especially how they end up written sometimes (i.e. with zero explanation)
If a test covers a single unit, is well put together, and well named, it's generally the best documentation to have - it describes what's going on and proves it to boot. However, this rarely happens. :( -Adron On Sun, Feb 27, 2011 at 7:13 PM, Aeden Jameson <[email protected]>wrote: > I'm curious how much stock people on this list put in the idea that > tests serve as documentation. > > -- > Cheers, > Aeden > > Blog : http://aedenjameson.blogspot.com/ > Linked In: http://www.linkedin.com/in/aedenjameson > Blah Blah Blah: http://www.twitter.com/daliful > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > > -- *Adron B Hall* *Tech*: http://compositecode.com *Transit*: http://transitsleuth.com *Twitter*: http://www.twitter.com/adronbh -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
