Changes between Version 7 and Version 8 of Writing Layout Tests to test iOS UI features
- Timestamp:
- Sep 30, 2015 3:48:45 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Writing Layout Tests to test iOS UI features
v7 v8 130 130 }}} 131 131 132 If your UI-side script is very simple and only accesses uiController properties, then it doesn't need to call uiScriptComplete(). If you call any uiController functions that are asynchronous (i.e. take a callback), then you need to call uiScriptComplete() at some point. 133 132 134 You can chain as many asynchronous things as you like in the UI-side script, as long as you call uiScriptComplete() when the chain is complete. You can also call testRunner.runUIScript() as many times as you like from the test content, making it possible to test a long sequence of operations that bounce between the UI process and the web process. 133 135 136 = Future enhancements = 134 137 138 UIScriptController will grow to allow tests to drive more behaviors in the UI process, for things like the keyboard, key events, selection, callouts etc.. We will also likely add ways to read back UI process state, like the state of the selection handles and callout bars.