Comment on page
@Oebs
Description: This keyword or action instructs ICE to close the running OEBS application.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
CloseApplication | NA | (optional) | NA |
Find the snippet of the keyword below:
For the above keyword, after the test case debug, the application under test will be closed and the execution status “True” / “False” will be stored in the output variable (if specified).
Description: This keyword or action instructs ICE to find the window specified in the input field and set the focus on that window.
Note:
- 1.This step should always be the first step for OEBS app type and this step is mandatory for every test case.
- 2.Window Name should be exact as oracle window name.
- 3.AUT should always be in the foreground to execute the OEBS keywords.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
FindWindowAndAttach | <Oracle Application Window Name> | (optional) |
|
Find the snippet of the keyword below:
In the above example after the test case debug, the application will select the provided window and the execution status “True” / “False” will be stored in the output variable (if specified).
Description: This keyword or action instructs ICE to launch the specified Java application.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
LaunchApplication | <java file path with extension>; <Name of the application> | (optional) |
|
Note: Launch application is mainly used for java applications.
Find the snippet of the keyword below:
In the above example, after the test case debug, the specified application will be launched and the execution status “True” / “False” will be stored in the output variable.
Description: This keyword or action instructs ICE to switch from present frame to frame specified in the input field.
Keyword | Input Syntax | Output Syntax | Supported Input Formats |
switchToFrame | <Frame Name> | (optional) |
|
Note:
- The specified frame name should be an exact match.
- Multiple usages of the 'switchToFrame' keyword within a single test script is restricted.
Find the snippet of the keyword below:
In the above example, after the test case debug, the focus will switch from the present frame to the Find Customer frame and the execution status “True”/ “False” will be stored in the output variable.
Last modified 7mo ago