Release 19.11

Perfecto Connect

Perfecto Connect, a secured network connection that supports testing Mobile or Web apps hosted on the local development network, is now available upon request. To access this feature, contact Perfecto Support.

The Perfecto Connect feature opens a direct connection between Perfecto Lab devices and a local network/backend server or a staged app that is not publicly available in other environments. This dedicated tunnel connection precludes the need for opening a VPN tunnel or defining the Perfecto Lab in the IP allow list of the development network.

Perfecto Connect involves:

  • Using a simple client command-line interface to establish the dedicated tunnel to the Perfecto Lab
  • Selecting devices in the automation script and associating them with the relevant tunnel
  • Running the tests on the applications that reside in the secure zone of the development network

The key values of the Perfecto Connect solution include:

  • Supports mobile devices and desktop web (fast web Windows devices only)
  • Fits any digital interactive, automation, and CI test executions
  • Requires no installation (just execute the client application)
  • Associates multiple devices with the same tunnel
  • Supports tunnel initiation from MacOS, Windows, and Linux workstations
  • For debugging and troubleshooting, supports bridging proxies (installed on a workstation), including support for Charles proxy and others
  • Allows for debugging over real devices from your local network/backend environment

Perfecto Connect currently does not support:

  • Devices running Android 9.0
  • MacOS

For more information, see the Perfecto Connect documentation. 

Mobile Device Selector

For mobile devices, you can now view the following information:

  • Devices currently in error state. A Contact Support button allows you to open a ticket with Perfecto Support asking to recover the device.

  • Who is using a device. This is helpful if you need access to a device currently in use by someone else. If the user’s email address is available in the system, the UI provides a link to the default email client configured.

Smart Reporting

The Groups panel in the Report Library view now includes a sorting option. Clicking the sort by icon  lets you sort by name (default), percentage of failed tests, and percentage of blocked tests.

Limitations

The following limitations apply:

Solved Issues

Perfecto resolved the following issues in this release:

  • NP-38413: In the legacy UI, when Appium scripts ran on iOS devices with session sharing, Appium drivers would not be created correctly. This is now fixed.
  • NP-38427/NP-38403: Perfecto did not support native application commands (activate_app, app_installed, app_state, remove_app and terminate_app) in Appium-specific Ruby clients. This is now fixed.

Product Updates

Important: API Change (effective as of release 19.10): Because the API used to implement the IDE gesture command or the Perfecto extension mobile:touch:gesture for iOS has been deprecated, we have update its implementation to be based on a newer API. While the new API performs more accurately and consistently, in some cases, parameter values in existing scripts may trigger different behavior and may need to be updated.
Important: When working with any beta version of major OS versions, especially but not only developer betas that are not available as public betas, any testing done on the device may be affected by instabilities and bugs on the OS level. If you are interested in testing a beta version, contact Perfecto Support or your Customer Success Manager. Consider limiting beta testing to 1-2 devices.

Android support updates

  • Support for Android 10 beta 6 with the below limitations: Video is not supported when a device is in "landscape" mode.

iOS support updates

  • Support for iOS 13.1 and iPadOS 13.1 Beta 2 with the following limitations: Touch & MultiTouch Actions executed by coordinates may not be performed on specific device models.
  • Support for iOS 13 and iPadOS 13 8th developer beta with the following limitations: Due to a bug in iOS 13, opening a SFSafariViewController class from a view controller that is not the main view controller causes the objects inside the controller to be inaccessible.