UiWatcher
public interface UiWatcher
See registerWatcher on how to register a a condition watcher to be called by the automation library. The automation library will invoke checkForCondition() only when a regular API call is in retry mode because it is unable to locate its selector yet. Only during this time, the watchers are invoked to check if there is something else unexpected on the screen.
Summary
Public methods |
|
|---|---|
abstract boolean |
Custom handler that is automatically called when the testing framework is unable to find a match using the |
Public methods
checkForCondition
abstract boolean checkForCondition()
Custom handler that is automatically called when the testing framework is unable to find a match using the UiSelector When the framework is in the process of matching a UiSelector and it is unable to match any widget based on the specified criteria in the selector, the framework will perform retries for a predetermined time, waiting for the display to update and show the desired widget. While the framework is in this state, it will call registered watchers' checkForCondition(). This gives the registered watchers a chance to take a look at the display and see if there is a recognized condition that can be handled and in doing so allowing the current test to continue. An example usage would be to look for dialogs popped due to other background processes requesting user attention and have nothing to do with the application currently under test.
| Returns | |
|---|---|
boolean |
true to indicate a matched condition or false for nothing was matched |