googletesting: TotT: Making a Perfect Matcher

TotT: Making a Perfect Matcher

Monday, October 5, 2009

by Zhanyong G. Mock Wan in Google Kirkland
Google C++ Mocking Framework matchers can make both your test code and your test output readableIt's easy to create a matcher that does exactly what you want, either by composing from existing matchers or by writing one from scratchcomposite matcherNot(m)mAnyOf(m1, ..., mn)ORAllOf(m1, ..., mn)ANDEXPECT_THAT(new_code, AnyOf(StartsWith(“// Tests”)),
              Not(ContainsRegex(“TODO.*intern”))));
Expected: (starts with “// Tests”) or
          (doesn't contain regular expression “TODO.*intern”)
Actual: “/* TODO: hire an intern. */ int main() {}”
The MATCHER macro lets you define a named matcherMATCHER(IsEven, “”) { return (arg % 2) == 0; }
EXPECT_THAT(paren_num, IsEven())notany codeautomatically generateExpected: is evenYou can also give multiple parameters to a matcher, or customize its description// P2 means the matcher has 2 parameters. Their names are low and high.

MATCHER_P2(InClosedRange, low, high, “is in range [%(low)s, %(high)s]”) {
  return low <= arg && arg <= high;
}
...
EXPECT_THAT(my_age, InClosedRange(adult_min, penalty_to_withdraw_401k)); Expected: is in range [18, 60]
  Actual: 2
Google C++ Mocking Framework uses compiler type inference to “write” the matcher parameter types for youToilet-Friendly Version

Testing Blog

TotT: Making a Perfect Matcher

No comments :

Post a Comment

Labels

Archive

Feed

Company-wide

Products

Developers