We make the disctinction between the actions to manage the channels in the ATS scripts, which is the subject of this documentation and the management of the channels in the editor to make operations of capturing graphical elements that you can read here .
In an ATS script generated by Agilitest, there is always only one active channel at a given time, and all actions are directed to that channel.
It is therefore imperative to start a channel before creating any action.
Start a channel
The start channel action allows you to select the application that Agilitest will launch for you, you have several possibilities:
- Open a browser among those proposed
- Open a Windows Explorer
- Open a desktop application defined in your configuration
- Open a mobile app (Android or iOS)
- Open any .exe application.
- Open a Webservice
You must then rename the channel you have opened so that you can reference it in the following actions. This is done by clicking on the little blue pencil.
The "Switch channel" action allows you to switch to another channel identified by its name.
From this action, all the following actions will be directed to the specified channel.
TIP : The starting of a new channel directly activates this one.
Stop a channel
Stopping a channel tells Agilitest that this channel will no longer be used during this test, and will close the application.
Connect a channel to an already launched application
A small trick: if you want to connect a channel to a process already existing in your operating system, you can use the process:\\ command completed by a regular expression to find your process in the list of processes already launched.
Channel management menu
This documentation is about the menu that allows you to manage the different action input channels when debugging tests, another article deals with channel management actions.
The channel management menu is on the left, below the project explorer
It has several icons whose functions are as follows:
Capture: This action is only possible if you have already opened a channel, executed the open action and possibly navigated to the page or web service you are testing. It allows to enter in capture mode and select elements on which to carry out actions.
Close: This action allows you to cleanly close an open channel, ie close the application and indicate to Agilitest that it is closed. Agilitest is not intrusive (no plugin), it has no way of knowing that you have closed an application directly through the actions of the operating system (click on the cross icon of the window for example) . It is therefore imperative to always use this action to close an application opened by Agilitest.
Run: This action starts a complete run from the current action. If you are not sure about an action to start a test, you will get the following message:
In Agilitest, all scripts can be sub-scripts of other scripts. In the editor, it is impossible for Agilitest to determine the beginning of a test, so you must indicate by which action you want to start your test in the editing and debugging phases.
Next: This action executes the selected action and moves on to the next action. So you can run your test in sequence, step by step. This action is equivalent to the action of executing each action displayed to the right of the current action in the editor.
Settings: This action displays a submenu for selecting the current execution settings in the editor.
- Animate: allows you to replay the test by animating the actions that are performed (moving the mouse, clicks, text entries, etc.).
- Visual Report: The visual report has the same result as the animation, but as a video report: an ATSV (ATS Video) file is generated in the /target/reports directory. It is not necessary to set the replay in animation mode to obtain the visual report.
- XML Report: Agilitest will produce a test execution report in XML format (actions.xml), as well as a set of images corresponding to the screens that were visited by the test. These elements are stored in the /target/report/<test_name> directory. They can then be manipulated to produce all types of reports, including a pdf report using FOP, as well as a style sheet that you have customized. Producing an XML report activates the generation of a visual report.
- Run in reduced mode: This hides the Agilitest editor during the execution of the test, and thus to better see the tested application. It's quite useful if you use Agilitest on one screen.