stratum domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114ultimate-member domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114um-recaptcha domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114wp-maximum-upload-file-size domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114wp-optimize domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114iksm domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114ultimate-addons-for-gutenberg domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114astra domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/soliterata.com/wp-includes/functions.php on line 6114
Documentation V 3.5 Overview Welcome to Solitera Test Automation Documentation! Here, you can find all the necessary information about Solitera Test Automation. After reading this, you will be able to use our tool more efficiently. System Requirements
Desktop step-Definition click on desktop window element at current cursor location for {string} times Keyword Given, When, And, Then Description Will click on the current desktop window multiple times Declaration Code Element Application Test Data Then click on desktop window element at current cursor location for “5” times NILL NILL NILL Remarks NILL Restriction Make sure the element is visible and clickable Table of contents Keyword Description Declaration Remarks Restriction
click on desktop window element at current cursor location for {string} times Read More »
Desktop step-Definition check timer for desktop application is within {string} milliseconds Keyword Given, When, And, Then Description After stopping the timer will check if the given value is inside the elapsed time or not. Declaration Code Element Application Test Data Then check timer for desktop application is within “15000” milliseconds ” InputField XPATH //input[@id=”Input”] ” NILL NILL Remarks NILL Restriction The desktop window should be accessible and in focus. The timer must be start before using this step def. Table of contents Keyword Description Declaration Remarks Restriction
check timer for desktop application is within {string} milliseconds Read More »
Desktop step-Definition stop timer for desktop application Keyword Given, When, And, Then Description Stop the already started timer Declaration Code Element Application Test Data Then stop timer for desktop application NILL NILL NILL Remarks NILL Restriction The desktop window should be accessible and in focus. The timer must be start before using this step def Table of contents Keyword Description Declaration Remarks Restriction
stop timer for desktop application Read More »
Desktop step-Definition get NativeWindowHandle from desktop application of element {string} and store as {string} Keyword Given, When, And, Then Description Will get the native window handle of the given element, try to pass the top element so that It can be used to switch to that window later on. Declaration Code Element Application Test Data Then get NativeWindowHandle from desktop application of element “InputField” and store as “ProgramFiles” ” InputField XPATH //input[@id=”Input”] ” NILL NILL Remarks This step is used to switch on the native window of the desktop application by using their top element. Restriction Element and application file should be in xml format. The desktop window should be accessible and in focus. Ensure that “element_name” is a valid and unique identifier. Table of contents Keyword Description Declaration Remarks Restriction
Desktop step-Definition switch focus to desktop window whose NativeWindowHandle is {string} Keyword Given, When, And, Then Description switch focus to desktop window element, whose Native window handle has been passed. Declaration Code Element Application Test Data Then switch focus to desktop window whose NativeWindowHandle is “NativeWindowName” NILL NILL NILL Remarks This step definition switches the focus to a window with the specified class name “String Value” and ensures that the switch is completed within the specified maximum time. Restriction The window with the specified class name “String Value” should be open and accessible. The “max” value should be a valid time (in milliseconds) for the maximum waiting time. Table of contents Keyword Description Declaration Remarks Restriction
switch focus to desktop window whose NativeWindowHandle is {string} Read More »
Desktop step-Definition start the server Keyword Given, When, And, Then Description Will start the appium and Winapp driver, IF you use this you have to switch to application you want to work on Declaration Code Element Application Test Data Then start the server NILL NILL NILL Remarks This step sends the specified text to a desktop window element using the image path specified by “String Value.” Restriction The specified image path should be valid and accurately represent the target element. The desktop window should be accessible and in focus. Table of contents Keyword Description Declaration Remarks Restriction
Desktop step-Definition right click on current pointer location in desktop window Keyword Given, When, And, Then Description will right click at the current cursor location Declaration Code Element Application Test Data Then right click on current pointer location in desktop window NILL NILL NILL Remarks NILL Restriction NILL Table of contents Keyword Description Declaration Remarks Restriction
right click on current pointer location in desktop window Read More »
Desktop step-Definition Hover over desktop element {string} and verify that the tooltip doesnot contains the text {string} Keyword Given, When, And, Then Description Will hover over the particular element and verify if the given tooltip does not contain the text Declaration Code Element Application Test Data When Hover over desktop element “InputField” and verify that the tooltip doesnot contains the text “Course” ” InputField XPATH //input[@id=”Input”] ” NILL NILL Remarks This step definition hovers the mouse over an element with the name “element_name” in the desktop window and verify the text value is visible or not. Verifying element visibility is a fundamental step in UI automation. Restriction The element with the name “element_name” should be accessible and hoverable in the desktop window. Make sure element name is correct and visible on the screen. Confirm that the verification correctly identifies the visibility state of the element. Table of contents Keyword Description Declaration Remarks Restriction
Desktop step-Definition Hover over desktop element {string} and verify that the tooltip displays text {string} Keyword Given, When, And, Then Description Will hover over the particular element and verify if the given tooltip displays text Declaration Code Element Application Test Data When Hover over desktop element “InputField” and verify that the tooltip displays text “Solitera” ” InputField XPATH //input[@id=”Input”] ” NILL NILL Remarks This step definition hovers the mouse over an element with the name “element_name” in the desktop window and verify the text value. Verifying element visibility is a fundamental step in UI automation. Restriction The element with the name “element_name” should be accessible and hoverable in the desktop window. Make sure element name is correct and visible on the screen. Confirm that the verification correctly identifies the visibility state of the element. Table of contents Keyword Description Declaration Remarks Restriction
Hover over desktop element {string} and verify that the tooltip displays text {string} Read More »
Solitera may collect certain information by automated means, such as cookies and web beacons, when a user visits our website. A “cookie” is a small piece of data that a website can send to your browser, which may then be stored on your system. learn more
