We will discuss the publishing facilities of the Agilitest editor.
The simplicity of the display
The Agilitest editor has been designed to show you most of the actions that you declare in your tests, for the details, it is usually enough to click on the displayed elements to make appear a complementary window which allows to go into the details.
There is a notion of active action: it is surrounded in black. All actions adding operations will be based on this notion.
It is possible to select several active actions: for this select the first action, press the SHIFT key on your keyboard and select the last one: all the actions between these two actions will be selected.
By using the CTRL key it is possible to separately select one or more actions to add to the group of active actions.
The creation of new actions
There are three ways to create new actions:
By clicking on the actions menu
You add a new action under the active action or the last active action. This new action appears empty of any information. It will then be necessary to complete manually or by dropping new elements on it.
By dropping a captured item on the tested application.
Just place the mouse in the lower part of the action below you want to create the new action to display a menu "Create an action".
Subsequently, the action that is generated is linked to a graphical element of your application: not all action types are accessible in this way.
Using the copy and paste function
By right-clicking on an action or group of active actions, you can display a context menu.
This menu will allow you to Cut / Copy and Paste, or even delete the selected actions.
Another option allows to activate or deactivate one or more actions: their display will be gray and they will not be replayed in the test.
Actions related to the elements of the application
All actions related to the elements of the tested application include a link to an interface element (issued from the tested software user interface).
For these actions, the upper part concerns the action performed, and its sub-menu is related to the specificity of this action.
The contextual menu linked to the interface element makes it possible to modify, or to completely manually specify the locator which makes it possible to find the element in the page:
By hovering over and clicking on the item you will see a popup menu with the following options:
Action on the element
By clicking on the item, you can add parents, children, specify their type completely manually.
By clicking on the small lego icon on the right, you can add attributes to the element.
Finally, a click on the # in the locator modification menu will allow you to indicate which element to select in order of appearance when your locator makes it possible to retreive several elements from the page. This feature is useful for selecting a specific row or column in a table for example.
Drag-drop of an element
By clicking on the dark banner of the interface element, you will be able to drag-drop it into a new action.
This is very useful for reusing interface elements that have already been previously declared
If you delete any definition of the interface elements of your application, you display the notion of root of the application, with the following possibilities:
- Add an interface element, we then return to the cases presented above.
- Click on a system button: this allows you to send a click event directly to the graphical components of your browser.
- Manage a modal dialog box of type alert or config: allows you to accept or refuse when the dialog box is displayed
- Add a locator to a system interface element: This function is related to desktop type locators. It is accessible to make manual modifications, but we advise you rather to go through the desktop driver.
A set of additional functions are available on an action line and will allow you to:
- Add a breakpoint when running the test, for debugging purposes. just click on the STOP panel
- Increase or decrease the maximum number of trials. This specifies to Agilitest that it must try several times to wait for the application to return before generating a failure. By default the value is set to 10, the possible values are from -10 to 50, and you should know that the higher the value, the more Agilitest will wait between two tests.
- Tell Agilitest that this action can fail: by clicking on the top right square, you will see a double green arrow indicating that the action can fail without the test failing. This feature is necessary to compensate for some sporadic behavior of applications, for example a popup that does not display all the time.