Discussion

This method is used internally by SLUIAElement and its subclasses SLElement and SLStaticElement. It should not need to be used by additional descendants of SLUIAElement.

Discussion

When asked to access their corresponding elements, instances of SLUIAElement automatically wait for those elements to become valid, for not more than this timeout value. If that access requires simulating user interaction, instances of SLUIAElement will additionally wait, for the remainder of the timeout, for their corresponding elements to become tappable.

This means that tests rarely need to wait for the user interface to update before attempting to access or interact with interface elements.

Discussion

Clients change this value by setting the default timeout used by the shared test controller ([SLTestController setDefaultTimeout:]) before testing begins.

Discussion

This should return YES unless the specified element identifies an instance of UIScrollView and tests are running on an iPad simulator or device running iOS 5.x. On those platforms, UIAutomation reports that scroll views are always invisible, and thus not tappable.

If this method returns NO, tappability will not be enforced as a prerequisite for simulating user interaction. This will let Subliminal attempt interaction with scroll views despite UIAutomation’s response. Testing reveals that certain forms of interaction, e.g. dragging, will yet succeed (barring factors like the scroll view actually being hidden or having user interaction disabled, etc.).

Discussion

The image is viewable from the UIAutomation debug log in Instruments.

When running subliminal-test from the command line, the images are also saved as PNGs within the specified output directory.

Discussion

Discussion

Each offset specifies a pair of x and y values, each ranging from 0.0 to 1.0. These values represent, respectively, relative horizontal and vertical positions within the element’s rect, with {0.0, 0.0} as the top left and {1.0, 1.0} as the bottom right.

This method uses a drag duration of 1.0 seconds (the documented default duration for touch-and-hold gestures according to Apple’s UIAElement class reference).

Discussion

That is, whether the receiver is first responder.

Discussion

Below iOS 7, this defaults to the midpoint of the element’s rect; at or above iOS 7, this defaults to the element’s accessibility activation point accessibilityActivationPoint]).

If the default hitpoint cannot be tapped, this method returns an alternate point, if possible.

Discussion

The user interface element represented by this element defines what “enabled” means. When the interface element is an instance of UIControl, this returns the value of that control’s -isEnabled property. This method otherwise appears to evaluate to YES.

Discussion

Unlike isVisible, this method will not raise an SLUIAElementInvalidException if the element is not valid—it will just return NO. This allows test writers to wait for an element to disappear without having to worry about whether the element will become invisible or simply invalid.

Discussion

All methods that simulate user interaction with an element require that that element be tappable. When a method involving user interaction is invoked on an SLUIAElement, that method will wait up to the default timeout for the element to become valid, and then will wait for the remainder of the timeout for the element to become tappable. If the element does not become tappable within that interval, the method will raise an SLUIAElementNotTappableException.

This method returns, or raises an SLUIAElementInvalidException, immediately.

Use of the UIAElement macro can help tests diagnose tappability failures.

Discussion

An element’s state can be accessed if and only if it is valid.

This method returns immediately. All other methods, unless marked otherwise, wait up to default timeout for the element to become valid, and raise an SLUIAElementInvalidException if the element does not become valid within that interval.

Use of the UIAElement macro can help tests diagnose validity failures.

Validity is not cached, but is determined anew every time a SLUIAElement is asked to access a corresponding interface element.

Discussion

This method returns immediately, but unlike isVisible, will not raise an SLUIAElementInvalidException if the element is not valid—it will just return NO. This allows test writers to wait for an element to appear without having to worry about whether the element is valid at the start of the wait.

Discussion

This method returns, or raises an SLUIAElementInvalidException, immediately.

Discussion

The information that is logged is determined by UIAutomation.

Discussion

The information that is logged is determined by UIAutomation.

Discussion

The relevant coordinates are screen-relative and are adjusted to account for device orientation.

Discussion

Discussion

The tap occurs at the element’s hitpoint.

Discussion

The UIAutomation representation identifies the UIAElement corresponding to the specified element to UIAutomation.

This method allows an element to evaluate more complex JavaScript expressions involving its corresponding UIAElement than simple function calls (for which waitUntilTappable:thenSendMessage: may be used); or to use a non-standard timeout for resolving the corresponding UIAElement.

This method waits until the element is valid before attempting to access the UIAElement, for not more than timeout. If waitUntilTappable is YES, the method will also wait, for the remainder of timeout, for the element to become tappable.

Discussion

The “message” is a formatted function call. For instance, SLUIAElement calls tap() on its corresponding UIAElement by invoking

[self waitUntilTappable:YES thenSendMessage:@"tap()"]

This method automatically waits until the element is valid before attempting to access the UIAElement, for not more than the default timeout. If waitUntilTappable is YES, the method will also wait, for the remainder of the timeout, for the element to become tappable.