Step for arbitrary logic on element #148

Closed
wants to merge 2 commits into
from

Conversation

Projects
None yet
4 participants

matvore commented Aug 22, 2012

This is for executing arbitrary interaction and verification logic on
a given view. Only the accessibility label can be specified, as
verification against the traits and value can be done manually on the
view in the execution block.

Contributor

mflint commented Sep 24, 2012

For what it's worth, I approve of this patch. Mucho helpful!

Contributor

blakewatters commented Sep 24, 2012

Another +1 for this. I've used KIF on half a dozen projects at this point and wound up with a variation of a similar step every time.

matvore added some commits Aug 22, 2012

@matvore @matvore matvore Implementing stepForViewWithAccessibilityLabel
This is for executing arbitrary interaction and verification logic on
a given view. Only the accessibility label can be specified, as
verification against the traits and value can be done manually on the
view in the execution block.
1af6b57
@matvore matvore Scroll to the element using _accessibilityElementWithLabel:...
If the element is not visible, the UIView will probably not exist and the
executionBlock will get the UIView that is visible and nearest to the
accessibility element in the hierarchy. This is not easy for the block to
predict and deal with, so use |_accessibilityElementWithLabel:| to make the
UIView visible.
77c3304

matvore commented Sep 28, 2012

Cleaned up commit history and added automatic scrolling to the element.

Contributor

bnickel commented Sep 16, 2013

Closing due to age. It may be worth taking a look at master/Documentation/Test Action Composition.md. Applying the approach from here to for tapViewWithAccessibilityHint: could yield a nice reusable mechanism for dealing with other non-label accessibility interfaces.

bnickel closed this Sep 16, 2013

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