Additional configurations can be performed on the flow's user actions. For this, Qualibrate has the Step Configuration and Object Properties tabs, which allow the user to customize the behavior of the user actions. To access the Step Configuration and Object Properties tabs, click on the target step. In the popup window you may find the following tabs:
You can also see the screenshot of the current step on the right side of the popup window.
Here is a videoguide on navigating through the technical information of the step:
You can customize the behaviour of the user actions by:
Changing the action type in the Actions dropdown list. Here you can also select advanced configurations for the Custom action type, which will allow you to add a custom advanced code.
Make the step optional.
Users can also add description/comment for each step of the flow sequence. One comment can be added/edited/removed for each step.
To add the description to a step:
Click on the target step. Popup window with the step configurations will be displayed.
Go to the Step Configuration tab.
Type your comment in the free text editor under Description section.
You can Save the comment by hitting Tab and Enter, or by pressing the Save button.
When recording an application, all the technical properties of the recorded objects are stored in this section. The user has the ability to edit, configure and fix the properties here.
Every user action that has been recorded is composed of the following elements, which affect the behavior of the execution of the action against the application:
User action type
The user action type dictates the type of activity that needs to happen on the target application. These activities range from clicking an element, setting a value on a field, or verifying information from an application.
These parameters are saved as variables in the data set related to the flow. Parameters start with prefix "P_".
Depending on the behavior of the user action, the parameter can be either an INPUT or OUTPUT parameter. OUTPUT parameters can be reused in other parts of the flow.
Two of the most important Recorder options are Verify and Store.
Action used to create a checkpoint for validating properties of an object in the application under test.
Action used to store a parameter generated by the application under test in order to have it available for future tasks.
Checkpoints are often used in automation testing to validate a properties of an object. You record your actions and in order to check that the results are according to your expectations you define a checkpoint.
Verifying that logon is successful would mean to validate the property of an object present on the first page after log on. During recording you choose a static property of an object to be checked at execution.
Choose a value on this screen to be checked during test execution so that it would validate that the test went well until this checkpoint. In this example we would verify a control text property. As a recommendation, it is best to choose a value that is likely to stay the same and that is specific to this SAP flow. In this example we will use the Verify action to check that after logging on to SAP the text of the top control you may see in the screenshot above contains the text “SAP Easy Access”.
Start a Recorder and connect and login to your SAP system.
Click on Verify button on the Recorder widget and click on the value you want to verify; in our case it will be the text “SAP Easy Access” of the top control.
Save the recording.
When the test execution will get to this step in will check that the value stored in the Qualibrate data set contains the value recorded for that control; in this specific case: “SAP Easy Access”. If the verification result is True, Qualibrate will continue the execution with the next task step. Otherwise, you will be prompted with an error.
If the SAP application will get updated afterwards and the text of this control will change, the value stored in the Qualibrate data set should be updated, too. Otherwise, the result of the Verify action will be False.
To see more information related to the recorded action expand the Recorder widget by clicking on the down-arrow next to the task name.
Expanded Recorder widget extra details:
User Action: Verify
Parameter name: P_GUITITLEBAR_TITL
Parameter type: INPUT
Recorded value: SAP Easy Access
For more configuration options please select the Configuration button of the Recorder option.
The Step Configuration window will be displayed showing BASIC configuration with the following information:
Select control property:
Current property value:
Verification test result:
The Select Control Property drop-down enables you to choose from the control property from the dropdown list.
There are also many options for the operations you want to include in the Verify action:
Greater than or equal to
Less than or equal to
Does not contain
The Store action is one of the most important actions in Qualibrate because it enables the user with the capability of storing an output value from the application under test and reuse it in another action from the same flow during an execution.
Store the sales order number after the document is created.
Start the Recorder;
Go on with the actions needed to be performed on SAP to create a sales order. After saving it the sales order number will be displayed on the bottom status bar like this:
3. Select the Store option in the Recorder widget and select the status bar as shown:
The SAP status bar text represents a concatenation of MessageParameter properties as you may see in more details by consulting the SAP Help documentation.
MessageParameter = "Standard Order"
MessageParameter = "15083"
MessageParameter = "has been saved"
4. You only need to capture the sales order number which is stored under MessageParameter. Therefore, expand the Recorder widget and go to the Basic Configuration window where we can choose the MessageParameter property of the SAP GuiStatusBar.
The default property captured by the Recorder is Text.
5. Change the Select Control Property from Text to MessageParameter
The Verification Test Result will represent now the sales number order we intend to store and reuse for our next Display Sales Order SAP flow.
6. Save the recording
Verify and Store functions have only the basic setting
If you want to further optimize the handling of the verify or store function, you can change the action to → Custom
Changing the action to “Custom” will port the configuration into a code snippet
To persist the new “Custom” action, you have to Save the configuration
If the configuration is not saved, the old “Verify” or “Store” configuration will be kept