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.