[mockitopp] r155 committed - add another sentence.

[mock...@googlecode.com]

Revision: 155
Author: plazt...@gmail.com
Date: Fri Jun 7 15:03:21 2013
Log: add another sentence.
http://code.google.com/p/mockitopp/source/detail?r=155

Modified:
/wiki/Argument_Matching.wiki

=======================================
--- /wiki/Argument_Matching.wiki Fri Jun 7 15:00:24 2013
+++ /wiki/Argument_Matching.wiki Fri Jun 7 15:03:21 2013
@@ -2,6 +2,8 @@
== Argument Matching ==
Usually, test cases are required to cover a large permutation of user
inputs. This can be troublesome in cases where the system under test has
several underlying dependencies. Usually, when using a mock framework to
provide the dependencies for the system under test, each dependency will
have to stubbed with 1:1 mappings of the user inputs. Overtime this makes
test cases quite brittle and becomes a maintenance liability. To help
reduce this overhead generic argument matchers are available
({{{<mockitopp/matchers>}}}) to use when stubbing method invocations. These
matchers work with all primitive types, but do note that complex types
(classes, etc) *must* implement operator==() correctly in order to be used.
If your complex types do not implement operator==, you will get a somewhat
messy compile error with lots of template expansion to sift through.

+The best examples of how to use mockitopp are it's own test source code
located in the test/ subdirectory. If you have problems using the examples
below, study the test source code.
+
=== Built-in ===
{{{
#include <mockitopp/mockitopp.hpp>