Desktop application operations – Page 9 – SoliteraTA

SoliteraTA

Demo
Login
Download

Desktop application operations


Deprecated: preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /var/www/html/soliterata.com/wp-includes/kses.php on line 1805

press {string} keys on current cursor location of desktop window

Desktop application operations, Input Operation /

Desktop step-Definition press {string} keys on current cursor location of desktop window Keyword Given, When, And, Then Description  press the keys on the current cursor location of the desktop window Declaration Code Element Application Test Data When press “ENTER” keys on current cursor location of 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

press {string} keys on current cursor location of desktop window Read More »

click on the {string} section of the splitbutton {string} on desktop window

Desktop application operations, Mouse Events Operation /

Desktop step-Definition click on the {string} section of the splitbutton {string} on desktop window Keyword Given, When, And, Then Description Will click on the specified section of the split button on the desktop window. Declaration Code Element Application Test Data When click on the “RIGHT” section of the splitbutton “InputField” on desktop window ” InputField ID Input ” NILL NILL Remarks This step clicks on a specific section with the name “String value” of a split button named “element_name” in the desktop window. Restriction The split button with the name “element_name” should be accessible and have a section named “String value.” Table of contents Keyword Description Declaration Remarks Restriction

click on the {string} section of the splitbutton {string} on desktop window Read More »

generate random text of length {string} and store as {string} in desktop window

Desktop application operations, Other Operation /

Desktop step-Definition generate random text of length {string} and store as {string} in desktop window Keyword Given, When, And, Then Description Will generate random text of a specified length from the desktop window and store it as a string Declaration Code Element Application Test Data Then generate random text of length “8” and store as “RandomText” in desktop window NILL NILL NILL Remarks This step allows generating random text of a specific length from the desktop window and storing it as a variable. Restriction The specified “String Value” must represent a valid length (integer) for the random text. The desktop window should be accessible and in focus. Table of contents Keyword Description Declaration Remarks Restriction

generate random text of length {string} and store as {string} in desktop window Read More »

enter random text of length “String Value” from desktop window and store as “Var_Name”

Desktop application operations, Desktop element interaction events /

Desktop step-Definition enter random text of length “String Value” from desktop window and store as “Var_Name” Keyword Given, When, And, Then Description Enter random text of a specified length from the desktop window and store it as a variable. Declaration Code Element Application Test Data When enter random text of length “7” from desktop window and store as “Text” 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

enter random text of length “String Value” from desktop window and store as “Var_Name” Read More »

enter text of variable “Var_Name” and send to “element_name” element in desktop window

Desktop application operations, Desktop element interaction events /

Desktop step-Definition enter text of variable “Var_Name” and send to “element_name” element in desktop window Keyword Given, When, And, Then Description Will send some string value and send it to an element Declaration Code Element Application Test Data When enter text of variable “Hello” and send to “InputField” element in desktop window ” InputField ID Input ” 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

enter text of variable “Var_Name” and send to “element_name” element in desktop window Read More »

click on desktop window element {string} for {string} times

Desktop application operations, Mouse Events Operation /

Desktop step-Definition click on desktop window element {string} for {string} times Keyword Given, When, And, Then Description Will click on the desktop window element multiple times Declaration Remarks Code Element Application Test Data When click on desktop window element “InputField” for “5” times ” InputField ID Input ” NILL NILL This step performs a click action on the element specified by “element_name” for multiple times within the desktop window. Restriction Element and application file should be in xml format. 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

click on desktop window element {string} for {string} times Read More »

press {string} keys on desktop element {string}

Desktop application operations, Input Operation /

Desktop step-Definition press {string} keys on desktop element {string} Keyword Given, When, And, Then Description Will press the key on element Declaration Code Element Application Test Data When press “ENTER” keys on desktop element “InputField” ” InputField ID Input ” 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

press {string} keys on desktop element {string} Read More »

right click on the desktop element {string}

Desktop application operations, Mouse Events Operation /

Desktop step-Definition right click on the desktop element {string} Keyword Given, When, And, Then Description Will right click on the desktop element Declaration Code Element Application Test Data When right click on the desktop element “InputField” ” InputField ID Input ” NILL NILL Remarks This step performs a right click action on the element specified by “element_name” within the desktop window. Restriction Element and application file should be in xml format. Ensure that “element_name” is a valid and unique identifier for the element you want to right click on. Make sure the element is visible and clickable before attempting the right click action. Table of contents Keyword Description Declaration Remarks Restriction

right click on the desktop element {string} Read More »

verify “String Value” from desktop window UI onclick value at location “element_name”

Desktop application operations, Verification /

Desktop step-Definition verify “String Variable” from UI onclick value at location “String Variable” Keyword Given, When, And, Then Description Verify if element is present on UI and click on it if present Declaration Code Element Application Test Data When verify “” from UI at location “userEmailField” ” userEmailField ID email ” NILL A Text1 Solitera 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

verify “String Value” from desktop window UI onclick value at location “element_name” Read More »

verify partial text “String Value” from desktop application UI at location “element_name”

Desktop application operations, Verification /

Desktop step-Definition verify partial text “String Value” from desktop application UI at location “element_name” Keyword Given, When, And, Then Description Verify partial text from a given UI element Declaration Code Element Application Test Data When verify partial text “Text1” from desktop application UI at location “InputField” ” userEmailField ID email ” NILL A Text1 Solitera Remarks  Verifying partial text can be useful when only a part of the content is relevant. Restriction Ensure that the partial text is correctly specified and element is correctly created. Table of contents Keyword Description Declaration Remarks Restriction

verify partial text “String Value” from desktop application UI at location “element_name” 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

Accept