Component Mobility Action Types

Last updated 1 year ago

Component Mobility Action Types

Welcome to Mobile action types, The purpose of this document is to explain about the action types used.

Launch :

Launch: Opens the app with the selected APK/IPA.

Go to URL: Navigates to the specified URL, used after opening a mobile browser
Required inputs :
- URL
- Description

Go Back:

This action either navigates you back one page in your browsing history or, if there's no previous page, returns you to the home screen.

Double Tap:

This action involves quickly tapping an element on the screen twice in succession. It's commonly used to:

Zoom In: On MobileActiontypesimages or web pages.
Select: To highlight or open items in some applications.
Activate: Trigger specific functions in certain apps or platforms.

Usage Contexts:

Mobile touch interfaces where a single tap might preview, and a double-tap might confirm or open.
Accessible software that may require double-tap for easier navigation.

Dynamic Double Tap:

This action is specifically designed to interact with elements that have dynamically generated values. Before executing this action, ensure the use of the "Create Variable" action type within Qyrus. This will allow capturing the dynamic value of the target element. Once stored, this value can be leveraged with the "dynamic double tap" action type, among other functionalities.

Required inputs :

Element’s Locator Type: The method through which the element is identified (e.g., ID, Name, XPath).
Element’s Value: Specific value associated with the chosen locator type.
Field Name: A dropdown menu that lists and lets you select the value of the specified element.

Optional Input:

Index Value of Element: This specifies which occurrence of the element to interact with if there are multiple matches. By default, it is set to '0' (indicating the first occurrence).

Long Press:

This action allows the user to execute a prolonged touch or click on a specific on-screen element.

Required inputs :

Element's Locator Type: The method used to identify the element (e.g., ID, Name, XPath).
Element's Value: The exact value corresponding to the chosen locator type.

Optional Input:

Index: In scenarios with multiple matching elements, this determines which occurrence to interact with. By default, it's set to 0, which targets the first occurrence.

Open Notifications:

This action activates the notifications panel, giving access to all recent alerts, messages, and system notifications on the phone.

Press Home:

This action involves pressing the 'home' button, which will navigate the user to the main screen or default interface of the device.

Tap:

Execute a tap or click on a distinct element within the interface.

Required inputs :

Element's Locator Type: The method used to identify the element (e.g., ID, Name, XPath).

Optional Input:

Index: In scenarios where there are multiple matching elements, this determines which occurrence to interact with. By default, it's set to 0, targeting the first occurrence.

Tap With Coordinates:

Execute a tap or click on a specific location on the page/interface using X and Y coordinates.

Required inputs :

Coordinates: Specify the exact X and Y coordinates on the interface where the action should be executed.

Swipe Gestures:

Custom Swipe: This action performs a swipe gesture on the interface, beginning at a specified starting point and ending at a designated endpoint.
Required inputs :
Coordinates
- Starting Point (x1, y1): The exact X and Y coordinates where the swipe gesture will begin.
- End Point (x2, y2): The precise X and Y coordinates where the swipe gesture will conclude.
Optional Input:
- Count: Determines the number of times the swipe gesture will be performed. By default, this is set to 1.

Swipe Down: This action executes a swipe down gesture on the device's interface. The frequency of the swipe can be determined in the optional data field.
Optional Input:
Swipe Element: This action initiates a swipe gesture on a particular element in the designated direction based on the provided coordinates.
- Locator: The method used to identify the element (e.g., ID, Name, XPath).
- Element's Value: The precise value corresponding to the chosen locator type.
- Field Value: Determines the number of times the swipe gesture should be performed. By default, this is set to 1.
Swipe Left: This action initiates a swipe left gesture on the device's interface. The frequency of the swipes can be determined by the provided data field.
Required inputs :
Swipe Right: This action initiates a swipe right gesture on the device's interface. The frequency of the swipes can be determined by the provided data field.
Required inputs :
Swipe Up: This action initiates a swipe up gesture on the device's interface. The frequency of the swipes can be determined by the provided data field.
Required inputs :

Close app:

This action terminates the currently open application on the device.

Get All Context:

This action displays a comprehensive list of all available views, interfaces, or screens within the application or platform.

Install:

This action facilitates the installation of an application while the component is in operation.

Required inputs :

Uninstall App:

This action facilitates the Uninstallation of an application.

Required inputs :

Field Value

Volume Up:

This will increase volume

Volume Down:

This will decrease volume of the device.

Landscape:

This action alters the phone's display orientation, switching it to a wider, landscape mode, ideal for viewing content that benefits from a horizontal perspective.

Portrait:

This action adjusts the phone's display orientation, switching it to a vertical, portrait mode.

Reset app:

This action involves terminating the currently active application and then promptly relaunching it.

Switch app:

This action facilitates switching and navigating between multiple applications on the device, enabling efficient multitasking.

Required inputs :

Field Value:
- For Android: Provide both the App Package and App Activity.

Switch Context:

In the context of hybrid applications, which combine native app components with web views, this action facilitates the shift of automation control from one web view to another, ensuring seamless testing and interaction.

Terminate app:

This action ensures the complete termination of a specified application, ending all its active processes and sessions.

Required inputs :

Field Value

Wait:

This action introduces a deliberate pause in the sequence of operations, holding for a defined duration before proceeding to the next step.

Required inputs :

Wait Until:

Waits for a specified amount of time.

Required inputs :

Max Duration: Duration in seconds

Wait Until Element Contains Text:

Waits until element contains text before proceeding to the next step.

Required inputs :

Max Duration: Duration in seconds
Expected value

Wait Until Element Has Text:

Waits until element has text before proceeding to the next step.

Required inputs :

Max Duration: Duration in seconds
Expected value

Wait Until Element Is Clickable:

Waits until element or button is clickable or it's not disabled before proceeding to the next step.

Required inputs :

Max Duration: Duration in seconds

Wait Until Element Matches Pattern:

Waits until element matches the pattern before proceeding to the next step.

Required inputs :

Max Duration: Duration in seconds
Expected value

Clear:

This action removes any data or input present in a specified field, returning it to its default or empty state.

Required inputs :

Element's locator type and value

Optional inputs :

Press keys:

This action simulates the pressing of specific keys on the phone's keyboard. If multiple keys need to be pressed simultaneously, they should be separated using the "+" symbol.

Required inputs :

Send text:

It will sends a value to a text field.

Required inputs :

Set:

This action allows you to input or set a specific text/string into a designated text field or adjust a spinner wheel to the desired value.

Required inputs :

Element's locator type and value
Field Value - Text to be placed in field

Set Clipboard Text:

This action updates the device's clipboard, overwriting its current content with a specified text. Once set, this allows for the text to be pasted elsewhere as needed.

Required inputs :

Field Value

Data Handlers:

Create Variable: Captures values from a specific element and stores it for future use. These values are typically dynamically generated.
Required inputs :
- Field Name - the name of the variable where the value of the element is stored
- Property - Is a dropdown field with two value(Text and Attribute) Note: When the property is selected as “attribute” , provide the attribute name in the Data field.

Dynamic Contains: This action assesses an element to determine if it contains the specific text mentioned in the Field Name field.
Dynamic Set: Inputs data into an element that has its text dynamically generated. Requires the use of the "Get" action type in Qyrus to find the dynamic value of that element and store that value so it can be used with the "dynamicset" action type.

Dynamic Verify: Verifies that an element, whose text is dynamically generated, has the value specified in the variable that stores the dynamic data. Requires the use of the "Create Variable" action type in Qyrus to find the dynamic value of that element and store that value so it can be used with the "dynamicverify" action type.

Dynamic Verify Is Not: Verifies that an element, whose text is dynamically generated, has the value specified in the variable that stores the dynamic data.

Get Clipboard Text: This action fetches the current content stored in the device's clipboard.

Get Element Count: Gets element count, whose text is dynamically generated, has the value specified in the variable that stores the dynamic data.
Required inputs :
- Element's Locator type and its value
Set Location: Sets the device's location by latitude, longitude and altitude. This action requires an altitude in addition to a latitude and longitude. Setting a wrong altitude value can yield improper data on an otherwise correct location.
Required inputs :
Verify OTP: Verifies the onetime password. You will manually enter the OTP into Qyrus once you receive on your device at run time.
Required inputs :
- Element’s Locator type and its Value.

Verifiers:

Contains: Checks if an element has the text specified in the Data field.
Required inputs :
- Element's locator type and its value
Is Blank: Checks if a text element is blank.
Required inputs :
Is Visible: Checks if an element is visible.
Required inputs :
Verify Attribute: Verifies the attribute of an element is the value specified in the Field Value.
Required inputs :
- Element’s Locator type and its Value.
- Field Value - value of the attribute that is to be checked.
Verify Attribute Is Not: Verifies the attribute of an element is not the value specified in the Field Value.
Required inputs :
- Element’s Locator type and its Value.
- Field Value - value of the attribute that is to be checked.
Verify Clipboard Text: Verifies some data is in the clipboard.
Required inputs :
Verify Push Notification Text: Verifies that the information in the notification is the specified text.
Required inputs :
Verify Text: Verifies the text of an element is the same as the value in the Field Value.
Required inputs :
- Element’s Locator type and its Value.
Verify Greater Than: Verifies the number provided in the field value of "Verify Greater Than" action type which is greater than the number for which the field is specified.
Required inputs :
- Element’s Locator type and its Value.
Verify Less Than: Verifies the number provided in the field value of "Verify Less Than" action type which is lesser than the number for which the field is specified.
Required inputs :
- Element’s Locator type and its Value.
Verify Not Null: Verifies if the value of the specified field is not null.
Required inputs :
Verify Regular Expression: Verifies the regular expression pattern provided in the field value of "Verify Regular Expression" action type for the specified field.
Required inputs :
- Element’s Locator type and its Value.

Element Verifiers:

Element Enabled: Checks that an element is enabled.
Required inputs :
Element Disabled: Checks if an element is disabled.
Required inputs :
Element Exist: Checks if an element exist.
Required inputs :
Element Not Exist: Confirm that an element does not exist.
Required inputs :
Element Position Is: Checks if an element is in the position specified by the value in the Field Value.
Required inputs :
- Element’s Locator type and its Value.
Element Position Is Not: Checks if an element is not in the position specified by the value in the Field Value.
Required inputs :
- Element’s Locator type and its Value.
Verify Element Count: Verifies the count of a specific element categorized by some similar locator info.
Required inputs :
- Element’s Locator type and its Value.

AI:

Click By Image: It clicks on the image which is uploded.

Required inputs :

Set By Image: Inputs a text into the element specified in the uploaded image.
Required inputs :
Verify By Image: Verifies the image uploaded.
Required inputs :

Start If:

This action signals the initiation of an Start If conditional statement. Every test or operation following this action type is nested within this condition. These subsequent steps will only be executed if the specified condition is satisfied.

End If:

to denote the end of the immediate above if condition.

Activate App:

This action involves bringing a specific application to the foreground, making it the active and currently-focused application on the device.

Required inputs :

Dynamic Tap:

This action involves interacting with an element on a screen. A "Dynamic Tap" action ensures that the desired element is correctly targeted and interacted.

Required inputs :

Dynamic Verify Attribute:

This action checks the value of a specific attribute within an element when the attribute value is dynamic or changes over time.

Required inputs :

Execute Query:

This action facilitates the execution of a specific database query, enabling the retrieval, modification, or deletion of data based on the query's purpose and structure.

Required inputs :

Query

Extract Words:

This action facilitates extracting specific words or data segments from a variable, especially when the variable is created using the "Create Variable" action type.

Required inputs :

Modify Dynamic Value:

Changes the data of a variable that is used with the "Get " action type.

Required inputs :

Remove Words:

Remove words from a variable that is used with the "Create Variable" action type.

Required inputs :

Swipe To Element:

Performs a swipe on a specific element which is not visible on the screen

Required inputs :

Element's locator type and value
Swipe direction

Tap By Relative Coordinates:

This action simulates a tap or click on a specific location on the screen, based on coordinates relative to a known reference point or element.

Required inputs :

Element's locator type and value

Execute Java Code:

Allows you to Execute a java code at runtime and also allows the you to determine whether the step has passed or failed.

Required inputs :

Code : user can paste the java code(JAVA Class) that they wishes to compile and execute.
Class Name : Name of the class that the user has entered in the code text area, that is to be compiled and executed.
Method Name : Name of the method that has to be executed within the java class entered by the user, the method has to take in one parameter of the type RemoteWebDriver.

Last updated 1 year ago