By Volume4
via java.dzone.com
Published: Oct 13 2008 / 09:18
Creating and using a mock object is semantically very much like using a stub, except that a mock will do a little more than a stub - it will save the history of communication so that it can later be verified. Let's add a new requirement to our LogAnalyzer class. It will have to interact with an external web service that will receive an error message whenever the LogAnalyzer encounters a filename whose length is not too long.
-
New Facebook Game Snooki Match
-
Applying E-Discovery Best Practices to Cloud Computing - All VoIP News
-
Cross page posting Submit Form Server.Transfer methods ASP.NET
-
What is Serialization? May be Star Trek analogy could help..
-
The Basics of Wireless Roaming Latency Analysis
-
One-to-many joins with Zend_Db_Table_Select
Add your comment
