kony.automation Namespace

The kony.automation Namespace consists of the following API groups.

Widget APIs

Widget Path

Widget ID from root element (form, and master, etc.). Comma-separated strings from root to widget represented in an array. It is applicable for almost all widget APIs.

NOTE: When you build an app in Test Mode, if the app contains components (with contract), the programmatic names of the properties must be unique. Ensure that the properties do not have the same name as that of any child widgets in the component or the parent FlexContainer widget. If a property and a widget (child or parent) have the same name, the property will not be honored.

NOTE: Whenever a Segment row is a part of Widget path, it refers to the top level flex. This flex ID should not be provided in the subsequent path.

Syntax

<widgetpath> [array of strings];

Mandatory/Optional

Mandatory

Examples

  • Each string denotes the widget ID in the hierarchy.

kony.automation.button.click(["frmHomeLogin", "btnLogin"]);

//Here, ["frmHomeLogin","btnLogin"]is the widget path.
  • The widget path string can consist of an array indexer for SegmentedUI widget to denote the corresponding row.


kony.automation.button.click(["frmHomeLogin", "segUi1[0,2]", "btnLogin"]);
kony.automation.button.click(["frmHomeLogin", "segUi1[2]", "btnLogin"]);
  • The widget path string can be a date for a Calendar cell template.

kony.automation.button.click(["frmHomeLogin", "calendar11[05,05,2016]", "btnLogin"]);
  • The widget path string can be the friendly name of a form.

kony.automation.button.click(["Login Page", "userwidget1", "btnLogin"]);

Platform Availability

  • Android
  • iOS
  • Responsive Web

The kony.automation Namespace comprises of the following Widget APIs.

Low-level Touch and Gesture APIs

The kony.automation Namespace comprises of the following Low-level Touch and Gesture APIs.

Miscellaneous Automation APIs

The kony.automation Namespace comprises of the following miscellaneous Automation APIs.

Cross App Testing APIs

From the V9 Service Pack 2 Fixpack 16 release, Quantum Visualizer introduces support for the following APIs for cross-app testing:

Page Object Model APIs

From the V9 Service Pack 5 release, Quantum Visualizer introduces support for the following APIs to support the Page Object Model approach in Jasmine Test Automation:

Existing Quantum Visualizer APIs

You can use the following existing Quantum Visualizer APIs for Automation. The respective syntax and usage remain the same.