I'll cherry pick the fix on the patch branch
plans for 2.2.1?
@kaidowei I experimented a bit more with the 1rst API draft and came up with this: http://pastebin.com/raw/dkCKD4YY
This possible 2nd draft should be more adequate than the first for mocking
(the syntax is inspired by mockito)
I haven't got the time to really make a full implementation, but it seems to be possible from the few tests I ran
I am also hesitating on the syntax of
mmk_when
there's
mmk_when (malloc, m,
.with_size = mmk_eq(size_t, sizeof (ref)),
.then_return = buf);of course, but
mmk_when (m, malloc(sizeof (ref)), .then_return = buf);seems really attractive
The biggest obstacle against syntax 2 are sequence points
this also opens the door to over the top control over parameter conditions
because then you could have easily something like:
mmk_when (m, foo(1, mmk_lt(0), mmk_arg_that(is_valid)), .then_return = 42);
and specify whatever matcher you want
can't you verify in the stub?
mmk_verify lets you check the number of times a function has been called based on predicates
Are you talking about
mmk_when vs mmk_verify?
mmk_verify asserts that at some point the function has been called with matching parameters a certain number of times
Both are complementary but not necessary to each other
If you want to test what happens when a function returns a specific value, you use
mmk_when (i.e. you tell a function to do things)
If you want to test how the function has been used (i.e. you ask the function if it has been called the way you want), then you use
mmk_verify
You can completely use
mmk_verify without mmk_when, and mmk_verify without mmk_when (useful when you don't care about return values)
what does mmk_eq do?
in my new batch of tests, it's simply
.with_foo = 42 instead of .with_foo = mmk_eq(type, 42)
there are other matchers though
like
mmk_any(type), which produces a dummy value matching any parameter
or
mmk_lt(type, val), which produces a dummy value matching any parameter less than val
btw, I'm surveying from a group of programmer friends what syntax they prefer between the two mentionned above, if you'd like to weigh in your syntactic preferences: http://goo.gl/forms/7CEBv3vvxT
(the one created by
test_stats_init)
