Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the 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 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultimate-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 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the um-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 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-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 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-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 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the iksm 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

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ultimate-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 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the astra 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
Ashish Kumar – Page 17 – SoliteraTA

SoliteraTA

Author name: Ashish Kumar

Ashish

drag element {string} in desktop window to the element{string} with offset of xcord {string} and ycord {string}

Desktop step-Definition drag element {string} in desktop window to the element{string} with offset of xcord {string} and ycord {string} Keyword Given, When, And, Then Description Will drag the element with the specified element in the desktop window to the provided offset of xCord coordinate. Declaration Code Element Application Test Data Then drag element “insertedRectangularShape” in desktop window to the element”F7_Cell” with offset of xcord “x1” and ycord “y1″ F7_Cell NAME F7 insertedRectangularShape XPATH //*[@Name=’Rectangle 1′ and @LocalizedControlType=’shape’] NILL NILL Remarks The element with the name “element_name” should be draggable, and it should be possible to drag it to the specified coordinates (x, y) in the desktop window. Restriction Ensure that “element_name” is a valid and unique identifier for the element you want to double-click on. Make sure the element is visible and clickable before attempting the double-click action. Table of contents Keyword Description Declaration Remarks Restriction

drag element {string} in desktop window to the element{string} with offset of xcord {string} and ycord {string} Read More »

double click on current pointer location in desktop window

Desktop step-Definition double click on current pointer location in desktop window Keyword Given, When, And, Then Description Will double click on the current cursor location. Declaration Code Element Application Test Data Then double click on current pointer location in desktop window NILL NILL NILL Remarks The Windows Application Driver (WinAppDriver) installed on your machine. You can download it from the  WinAppDriver v1.2.1. A windows machine with the desktop application you want to test installed. Inspect.exe should be present on your system to inspect the element of desktop application under test (Inspect .exe is a part of Microsoft SDK). Default winAppDriver location: C:Program Files (x86)Windows Application Driver Restriction Element and application file should be in xml format. Table of contents Keyword Description Declaration Remarks Restriction

double click on current pointer location in desktop window Read More »

Verify if input field element of desktop element {string} contains some value

Desktop step-Definition Verify if input field element of desktop element {string} contains some value Keyword Given, When, And, Then Description Will check if the input field element of desktop element contains some value Declaration Code Element Application Test Data Then verify if input field element of desktop element “A1_cell” contains some value A1_Cell NAME A1 NILL NILL Remarks Verifying element visibility is a fundamental step in UI automation. Restriction 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

Verify if input field element of desktop element {string} contains some value Read More »

Verify if input field of desktop element {string} is empty

Desktop step-Definition Verify if input field of desktop element {string} is empty Keyword Given, When, And, Then Description Will check if the input field of desktop element is empty Declaration Code Element Application Test Data Then verify if input field of desktop element “A1_cell” is empty A1_Cell NAME A1 NILL NILL Remarks Verifying element visibility is a fundamental step in UI automation. Restriction 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

Verify if input field of desktop element {string} is empty Read More »

verify attribute {string} of desktop element {string} is not eqauls to the value {string}

Desktop step-Definition verify attribute {string} of desktop element {string} is not eqauls to the value {string} Keyword Given, When, And, Then Description Will check if the attribute value of the specified element in the desktop window is equal to the provided value or not Declaration Code Element Application Test Data Then verify attribute “ClassName” of desktop element “A1_Cell” is not equals to the value “XLSpreadsheetCell” A1_Cell NAME A1 NILL NILL Remarks Verifying element visibility is a fundamental step in UI automation. Restriction 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

verify attribute {string} of desktop element {string} is not eqauls to the value {string} Read More »

verify attribute {string} of desktop element {string} is eqauls to the value {string}

Desktop step-Definition verify attribute {string} of desktop element {string} is eqauls to the value {string} Keyword Given, When, And, Then Description Will check if the attribute value of the specified element in the desktop window is equal to the provided value. Declaration Code Element Application Test Data Then verify attribute “ClassName” of desktop element “A1_Cell” is equals to the value “XLSpreadsheetCell” A1_Cell NAME A1 NILL NILL Remarks Verifying element visibility is a fundamental step in UI automation. Restriction 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

verify attribute {string} of desktop element {string} is eqauls to the value {string} Read More »

verify text {string} is not present on the desktop window

Desktop step-Definition verify text {string} is not present on the desktop window Keyword Given, When, And, Then Description Will check if the given text is not present in the window. Declaration Code Element Application Test Data Then verify text “SoliteraTA” is not present on the desktop window NILL NILL NILL Remarks Verifying element visibility is a fundamental step in UI automation. Restriction Make sure text is correct and visible on the screen. Confirm that the verification correctly identifies the visibility state of the text. Table of contents Keyword Description Declaration Remarks Restriction

verify text {string} is not present on the desktop window Read More »

verify text {string} is present on the desktop window

Desktop step-Definition verify text {string} is present on the desktop window Keyword Given, When, And, Then Description Will check if the given text is present in the window. Declaration Code Element Application Test Data Then verify text “SoliteraTA” is present on the desktop window NILL NILL NILL Remarks Verifying element visibility is a fundamental step in UI automation. Restriction Make sure text is correct and visible on the screen. Confirm that the verification correctly identifies the visibility state of the text. Table of contents Keyword Description Declaration Remarks Restriction

verify text {string} is present on the desktop window Read More »

verify text {string} is not present in desktop window element {string}

Desktop step-Definition verify text {string} is not present in desktop window element {string} Keyword Given, When, And, Then Description Will check if the given text is not present in the window element. Declaration Code Element Application Test Data Then verify text “SoliteraTA” is not present in desktop window element “FormulaBar” FormulaBar NAME Formula Bar NILL NILL Remarks Verifying element visibility is a fundamental step in UI automation. Restriction Make sure element name is correct and visible on the screen. Confirm that the verification correctly identifies the visibility state of the element. Ensure that “element_name” is a valid and unique identifier. Make sure the element is visible and readable before attempting any action. Table of contents Keyword Description Declaration Remarks Restriction

verify text {string} is not present in desktop window element {string} Read More »

verify text {string} is present in desktop window element {string}

Desktop step-Definition verify text {string} is present in desktop window element {string} Keyword Given, When, And, Then Description Will check if the given text is present in the window element Declaration Code Element Application Test Data Then verify text “SoliteraTA” is present in desktop window element “FormulaBar” FormulaBar NAME Formula Bar NILL NILL Remarks Verifying element visibility is a fundamental step in UI automation. Restriction Make sure element name is correct and visible on the screen. Confirm that the verification correctly identifies the visibility state of the element. Ensure that “element_name” is a valid and unique identifier. Make sure the element is visible and readable before attempting any action. Table of contents Keyword Description Declaration Remarks Restriction

verify text {string} is present in desktop window element {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