KWStringContainsMatcher is deprecated, should KWStringPrefixMatcher also be deprecated?

[jessedc]

I'm also busy looking for a non-deprecated way of matching arguments.

[[[ANotification should] receive:@selector(displayAlertWithIcon:message:) withArguments:any(), hasSubstring(@"Unable"), nil];

[sgleadow]

I think I contributed hasSubstring back in the day... I definitely want to be able to do fuzzy matches on arguments, so things like any(), anyNonNil() or hasSubstring(). Assume there is a new way that I'm not aware of, or is this functionality that no one else uses?

OCMock has always had pretty good argument matchers on mocks and stubs, but the syntax isn't as nice as Kiwi.

[Panajev]

I would argue OCMock's way of capturing any argument with OCMArg and implementing a matcher using either the default ones or a custom matcher using a block is both easier to read and easier to use than the spy system Kiwi uses.

[web [iPhone msg]]

On 27/feb/2014, at 04:10, Stewart Gleadow [email protected] wrote:

I think I contributed hasSubstring back in the day... I definitely want to be able to do fuzzy matches on arguments, so things like any(), anyNonNil() or hasSubstring(). Assume there is a new way that I'm not aware of, or is this functionality that no one else uses?

OCMock has always had pretty good argument matchers on mocks and stubs, but the syntax isn't as nice as Kiwi.

�
Reply to this email directly or view it on GitHub.