Qualibrate supports recording and executing key events on your application under test. The following key combinations are supported for the moment:
CTRL AND/OR ALT AND/OR SHIFT + ENTER OR F1 OR F2 … F12 OR "Any letter (A-Z)"
To define new key events you should access the Toolbox Setting configuration XML file.
Step1 Select Company Settings from top-right menu
Step2 Select Toolbox Settings from top-left menu
Step3 Add action to the technology section of the XML configuration file
The action of pressing the key or the key combination should be added under the actions tag of the technology and the object needed.
For example, pressing F2 should be first included in the technology section as follows:
<action name="Press F2" key="F2"/>
Obs: The action name should always start with the word 'Press'.
Step4 Add action to the object section of the XML configuration file
Pressing F2 on an SAP object of type GuiFrameWindow should have a similar structure:
<object name="GuiFrameWindow" type="GuiFrameWindow" attributes="" events="" value="">
<property name="Id" mandatory="True" />
<property name="Type" mandatory="True" />
<action name="Press ENTER" default="True" description="Press ENTER on XXOBJECTNAMEXX." has-input="False"/>
<action name="Press F2" default="False" description="Press F2 on XXOBJECTNAMEXX." has-input="False"/>
<action name="Press F3" default="False" description="Press F3 on XXOBJECTNAMEXX." has-input="False"/>
The action XML element has the following attributes:
1. Name - Name of the action that is being added to the object
2. Default - If set to true it will be the default action/method that will be recorded for that object.
3. Description - It is the name under which the action is recorded. For example Press F2 on XXOBJECTNAMEXX is replaced by Press F2 on WebPage. That's the resulting action name.
4. has-input - If set to true the engine records the INPUT parameter for that action. This is set to true usually for the Verify/Store and Type actions.