The Agilitest action menu is central and allows you to manually declare all possible actions in a test script.
Types of actions
These actions allow you to create, close and modify the current channel of your test. They are integrated directly into the script.
Start channel: This action allows Agilitest to make the link with the application under test.
Switch channel: This action is used when several channels are present in the script. It allows to switch between the different channels.
Close channel: This tells Agilitest that the channel will no longer be used during this test and will close the application.
In the case of application automation on remote services, Web and Webservices, these actions will allow you to indicate which URL to navigate to and which protocol to select: Web / HTTP, SOAP, REST.
In the case of an execution on the desktop, you will still have to go through the "Browser URL" action by entering the path of the tested application in the Windows Explorer.
This action does not have a drop-down menu because it directly creates a script call action in the script. Sub-scripts do not differ from scripts, both are ats files, only one is called by the other.
There are two ways to use this action:
- By making a direct call with or without parameters
- From a CSV/JSON file
Enter text action
The enter text action sends items corresponding to keyboard keys to your application, key presses, with or without additional special keys.
This action is inserted directly into your script. From the action you can set the nature of the action.
Click on the action "Enter text [ ]" to enter a text.
You can write directly the desired text with your keyboard. You also have access to the special keys which have the same functions as those present on the keyboard (enter, space, CTRL, etc...).
Also, you can insert special values into your text entry from the special value menu.
This will give you access to various values, variables, etc…
The mouse actions are used to manage the mouse on PC applications, but also the specific actions of mobile applications such as the swipe.
This action has a sub-menu including :
- Mouse click: It performs a click action on an element
- Over: It simulates the mouse over
- Drag and Drop: This action contains a sub-menu that completes it:
- Drag: This performs a hold click
- Drop: This releases the element. It must be preceded by a "drag" action
- Swiping: To swipe right, left, up or down with the mouse or by simulating touch for web tests.
- Scroll: To scroll a cursor or access elements of a page
Check actions are generated for an explicit check or assertion during the test. This can potentially lead to the test failing or allowing it to continue.
There are three possible verification actions:
- Property check: This allows you to check the value of an existing property in the script
- Occurrences check: This allows you to check the number of occurrences of an element
- Values check: This allows to verify that a value corresponds to an existing value in the script
The property action allows you, from a captured component, to retrieve one of its properties and place it in a variable.
This variable can then be used to define other dependent variables, create assertions, etc.
System actions are only used for a mobile channel.
This action is done in two ways:
- By using the button action: This allows you to interact with a physical button on the phone (sound setting, home, lock, etc...)
- By setting the properties: This allows you to define a system property (sound volume level, phone orientation, enable/disable WIFI, etc...)
The window management action allows you to manage the Windows operating system, Windows desktop modal applications and browser tabs.
It does not allow you to manage the internal windows of some web applications, which are floating HTML elements, directly accessible with the web automations.
A specific menu is also available to manage dialog boxes without adding unnecessary complexity.
The window action has a sub-menu with three possible actions:
- Size and location: This moves the window by specifying its new Cartesian coordinates or to change its size (height and width).
- Window visual state: This allows you to send an event from the operating system to the current window.
- Switch Window: This changes the current window by specifying the number of the window that should be swapped.
This action handles specific SELECT components in web browsers or COMBO-BOXES in desktop applications.
It differs from the Java execution action which occurs outside the context of a component (but which can still retrieve variables).
In addition to simple technical comments, this action will allow you to declare key functional steps in your test.
This action has four types of comments:
- Functional step: This comment indicates an important step in the script
- Script comment: This comment explains the operations performed by the script
- Execution log: This comment is functional on strings
- Report Summary: Allows you to add text to the summary of the generated execution report
Some of these actions can act directly on a component and can be created from an element captured and dropped into the script.