Operations
Keyword: LAUNCHAPPLICATION
Description: This keyword or action instructs ICE to launch the given application.
Find the snippet of the keyword below:
In the above example, after the test case debug, the application will be launched and connected to server1 and if the output variable is provided for execution status, “True”/ “False” will be stored in it.
Keyword: SERVERCONNECT
Description: This keyword or action instructs ICE to select the given server from the list.
Find the snippet of the keyword below:
In the above example after the test case debug, SAP Application will be launched and connected to the server “Server1” and if the output variable is provided for the execution status, “True”/ “False” will be stored in it.
Keyword: STARTTRANSACTION
Description: This keyword or action instructs the ICE to navigate to the transaction that the user requires.
Find the snippet of the keyword below:
In the above example after the test case debug, the user will be navigated to the Transaction Page MM01 and if the output variable is provided for the execution status, “True”/ “False” will be stored in it.
Keyword: TOOLBARACTION
Description: This keyword or action instructs the ICE to perform actions on the given SAP Toolbar button.
Find the snippet of the keyword below:
In the above example after the test case debug, ICE will perform a press/click operation on the SAP Toolbar button named “Generates shortcut” and if output variable is provided for execution status “True”/ “False” will be stored in it.
Keyword: GETPAGETITLE
Description: This keyword or action instructs ICE to fetch the title of the SAP Application and save the result in an output variable.
Find the snippet of the keyword below:
In the above example after the test case debug, ICE will fetch the page title and the value will be stored in variable {GPT}. If the output variable is provided for execution status “True”/ “False” will be stored in it.
Keyword: GETPOPUPTEXT
Description: This keyword or action instructs the ICE to fetch the text displayed in the pop-up of the SAP Application and save result in the output variable.
Find the snippet of the keyword below:
In the above example after the test case debug, ICE will fetch the text of the PopUp and the value will be stored in variable {GPPT}. If the output variable is provided for execution status “Fail”/ “Pass” will be stored in it.
Keyword: CLOSEAPPLICATION
Description: This keyword or action instructs ICE to close the SAP Application.
Find the snippet of the keyword below:
In the above example, after the test case debug, the application will be closed and if the output variable is provided for execution status, “True”/ “False” will be stored in it.
Keyword: DOUBLECLICKSTATUSBAR
Description: This keyword or action instructs ICE to double click on the Status Bar.
Find the snippet of the keyword below:
In the above example, after the test case debug, ICE will perform a double click operation on the status bar and if the output variable is provided for execution status, “True” / “False” will be stored in it.
Keyword: SELECTMENU
Description: This keyword or action instructs ICE to select the menu item.
Find the snippet of the keyword below:
In the above example, after the test case debug, ICE will open the menu item “Elements” -> “Table control” -> “Single.sel.cl” and if output variable is provided for execution status, “True”/ “False” will be stored in it.
Keyword: GETSTATUSBARMESSAGE
Description: This keyword or action instructs ICE to fetch the messages displayed on the Status Bar of the SAP Application and save the result in the output variable.
Find the snippet of the keyword below:
In the above example, after the test case debug, ICE will fetch the text of the Status bar and the value will be stored in the variable {message}. If the output variable is provided for execution status, “True”/ “False” will be stored in it.
Keyword: GETDIALOGWINDOWNAME
Description: This keyword or action instructs ICE to fetch the window name displayed on the dialog window of SAP Application and save the result in the output variable.
Find the snippet of the keyword below:
In the above example, after the test case debug, ICE will fetch the name of the dialog window and the value will be stored in the variable {message}. If the output variable is provided for execution status, “True”/ “False” will be stored in it.
Keyword: RESTOREWINDOW
Description: This keyword or action instructs ICE to restore the recently launched window of the SAP Application and save the result in the output variable.
Find the snippet of the keyword below:
In the above example, after the test case debug, ICE will restore the window. If the output variable is provided for execution status, “True”/ “False” will be stored in it.
Keyword: MINIMIZEWINDOW
Description: This keyword or action instructs ICE to minimize the recently launched window of the SAP Application and save the result in the output variable.
Find the snippet of the keyword below:
In the above example, after the test case debug, ICE will minimize the window. If the output variable is provided for execution status, “True”/ “False” will be stored in it.
Keyword: MAXIMIZEWINDOW
Description: This keyword or action instructs ICE to maximize the recently launched window of the SAP Application and save the result in the output variable.
Find the snippet of the keyword below:
In the above example, after the test case debug, ICE will maximize the window. If output variable is provide for execution status, “True”/ “False” will be stored in it.
Keyword: CLOSEWINDOW
Description: This keyword or action instructs ICE to close the recently launched window of SAP Application and save the result in the output variable.
Find the snippet of the keyword below:
In the above example, after the test case debug, ICE will close the window. If the output variable is provided for execution status, “True”/ “False” will be stored in it.
Last updated
