Applies to TestComplete 14.70, last modified on October 20, 2020
Information in this topic applies to hybrid mobile applications.

Hybrid Mobile options let you configure different aspects of TestComplete behavior when testing hybrid mobile applications.

Two notes:

  • These options are available only if you have a license for the TestComplete Mobile module and the module’s plugins are enabled in TestComplete.

  • Recommendation: Some of these options specify the way TestComplete names test objects. Changing these options can break the existing tests. We recommend that you configure the options before you start creating tests.

To view or modify the options, do any of the following:

  • Select Tools > Current Project Properties from the TestComplete menu.

    – or –

    Double-click the project in the Project Explorer. In the project editor that opens, select the Properties tab.

    – or –

    From the context menu of the project in the Project Explorer, select Edit > Properties.

  • In the tree on the left of the project properties editor, select Open Applications > Hybrid Mobile.

TestComplete Project Properties - Hybrid Mobile

Click the image to enlarge it.

You can change the following options:

  • Identification attribute - TestComplete uses the HTML id and name attributes to identify web page elements. This option specifies which attribute TestComplete should look at first when selecting an identifier for a web test object.

    If the selected primary attribute is not specified or if it is ignored due to matching one of the Dynamic identifiers, TestComplete tries the other attribute. If the secondary attribute is also missing or ignored, TestComplete uses the index as the object’s identifier. See the description of the ObjectIdentifier property.

  • Dynamic identifiers - Web applications can use dynamically generated ids (for example, ext-gen-123) that can change from session to session. This option specifies a list of patterns for detecting and handling dynamic identifiers in order to achieve more robust object recognition during test recording and playback. Depending on the pattern type and configuration, TestComplete either ignores the dynamic identifier or extracts and uses its stable, non-changing part. For more information, see Handle Dynamic Identifiers.

    There are predefined patterns for popular mobile web application frameworks, such as ASP.NET, jQuery UI, Dodjo toolkit and others.

    Pattern Settings

    Modifying the list

    To add a new group

    To add a new pattern via wizard

    To define a pattern manually

    To modify a pattern

    To check if a specific identifier matches one of the existing patterns

    To enable or disable a pattern

    To delete a pattern or group

     

  • Update WebView settings to allow access to frame elements - Android 4.1 and later restricts access to the contents of frames for pages loaded from local files. This option specifies whether TestComplete should change the settings of AndroidWebView controls to allow access to FRAME contents on these pages. If the setting is disabled, TestComplete has no access to web elements in FRAMEs on these pages.

    Note: If this setting is enabled, TestComplete reloads the page displayed in a WebView control when you first access a frame.

    To avoid reloading, you can allow access to the frame contents by modifying the properties of the tested WebView control from script. Learn more about this.

The default values for the web object identification options that will be used in new TestComplete projects can be specified in the Default Project Properties - Object Identification Options dialog.

See Also

Testing Hybrid Mobile Applications
Testing Hybrid Mobile Applications - Overview
Default Project Properties - Object Identification Options
Project Properties - Object Identification Options

Highlight search results