Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Added comparison macros for comparing two objects for equality. #176

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
3 participants

matvore commented Dec 7, 2012

These can be used in the same manner as KIFTestCondition and
KIFTestWaitCondition. Using these new macros will make logs more
helpful and make writing assertions a little easier.

Error strings contain both the Objective-C expression strings and the
expression values. For instance, if you do:

KIFTestEqual(x.foo, y.bar, ...)

then "x.foo" and "y.bar" will show up in the log output as well as
their actual values.

Added comparison macros for comparing two objects for equality.
These can be used in the same manner as KIFTestCondition and
KIFTestWaitCondition. Using these new macros will make logs more
helpful and make writing assertions a little easier.

Error strings contain both the Objective-C expression strings and the
expression values. For instance, if you do:

KIFTestEqual(x.foo, y.bar, ...)

then "x.foo" and "y.bar" will show up in the log output as well as
their actual values.
Contributor

bnickel commented Sep 11, 2013

What is the application of this for KIF? KIF mostly checks against functionality and object equality isn't a common use case.

matvore commented Sep 12, 2013

This is useful for writing custom steps in which you must do verification logic. For instance, if I have a custom step that checks if a view has a certain background color, I can use this to compare the NSColor objects. Upon failure, the log will include the "actual" and "expected" values of the color to help with debugging.

Contributor

phatmann commented Apr 7, 2014

I am closing any pull requests for KIF 1.0, as it will no longer be maintained.

@phatmann phatmann closed this Apr 7, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment