A while back I talked about how testable code helps manage complexity . In that post, I mentioned one common rebuttal to certain design decisions made in code in order to make it more testable. Why would I want to do XYZ just do improve testability? Recently, I heard one variation of this comment in the comments to my post on unit test boundaries . Several people suggested that it's fine to have unit tests access the database, after all, the code relies on data from the database, it should be tested. Implicit in this statement is the question, " Why would I want to abstract away the data access just to improve testability? " Keep in mind, I never said you shouldn't test your code's interaction with the database. You absolutely should. I merely...(read more)
Source Click Here.
A
New
Internet
Library: Add Your Website/Blog
or Suggest A Website/Blog to our Free Web Directory
http://anil.myfunda.net.
Its very simple, free and SEO Friendly. Submit Now....
Its very simple, free and SEO Friendly. Submit Now....
Monday, August 4, 2008
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
Post your comments here: