Last updated: Oct 15, 2019 10:00
The following limitations apply:
- The new architecture for Web and Hybrid automation is currently not supported on devices running iOS 13.
- Cross-domain scripting is not supported.
- With Appium/Selenium, using
executionAsyncScripton iOS causes the system to hang.
This also entails the use of async Protractor operations. When using Protractor, make sure to add a
browser.waitForAngularEnabled(false);command before executing other operations to disable async executions.
Enable the new Appium architecture
During the transition phase, you need to select the new architecture explicitly on a per-script basis using the following designated new capabilities. These capabilities control the architecture used for both web and hybrid.
To use the new architecture on all your scripts, you can ask Perfecto Support to update your cloud configuration to use the new architecture by default. If the new architecture is the default, you can omit the new capabilities shown in red below.
Note: To allow hybrid testing on a cloud device, the app is resigned with a Perfecto development certificate. Apps using special entitlements that require the original author's certificate may not work as intended after the resigning process.
Migrate existing Perfecto Hybrid app automation scripts to the new architecture
How you migrate existing Perfecto Hybrid app automation scripts to the new architecture depends on whether you work with single webview or multiple webview apps.
Single webview apps
Note: Due to open tabs in Safari, the driver might identify several webview contexts. However, the implementation automatically uses the old webview names when looking for a single active webview, so the commands
("WEBVIEW_1") both work as before. There is no need to search for the correct webview.
To migrate scripts for single webview apps:
Change the value of the
PerfectoMobileto its default value,
Appium. Alternatively, because
Appiumis the default value, you may remove this capability altogether.
Cancel the instrumentation (there is no need to instrument the tested app). Then fix object locators, if needed, because the tree seen by the script is slightly different.
Add the following capabilities with a value of
true(as described above):
Multiple webview apps
Working with multiple webview apps now requires the use of the Appium capability
fullContextList. Getting a list of all webviews using the
["NATIVE_APP", "WEBVIEW_2", "WEBVIEW_3"]
where each webview is appended with a non-descriptive number and the order is not guaranteed to be the same with every test run. When setting the value of the desired capability
) command returns the contexts as a JSON string. When parsed, each context is an object that includes:
- The ID of the webview
- The URL that the webview currently displays
- The title of the page
fullContextList capability is only supported when testing on iOS devices using the new architecture.
To migrate scripts for multiple webview apps:
fullContextListcapability to the driver and set it to
Retrieve the contexts via the
)command (in Java, you can then cast each context to
Select the required context by URL or title key and execute a context switch, as shown in the following example: