Step Defination – Page 15 – SoliteraTA

SoliteraTA

Step Defination

get NativeWindowHandle from desktop application of element {string} and store as {string}

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

get NativeWindowHandle from desktop application of element {string} and store as {string} Read More »

switch focus to desktop window whose NativeWindowHandle is {string}

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 »

start the server

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

start the server Read More »

right click on current pointer location in desktop window

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 »

Hover over desktop element {string} and verify that the tooltip doesnot contains the text {string}

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

Hover over desktop element {string} and verify that the tooltip doesnot contains the text {string} Read More »

Hover over desktop element {string} and verify that the tooltip displays text {string}

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 »

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 »

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