Editor presentation
To help you familiarize with the Agilitest environment, here is a presentation of the various elements that makes up the Agilitest editor.

Editor' side bar

This side bar is situated at the left of the editor. It contains multiple menus that can be used to create your tests.
Project menu

In this menu :
- New project
- Open project : To open an existing project from your window explorer
- New component : To add a component to your project (ATS script, data files,...)
- Project properties
- Project secrets : To open a window with the project's passwords and tokens
- Project users : To open a window with the users that use the current project and show their last modification
- Groups management : To open the groups management window
- Close project
Other side bar's menus

- Executions management : To open the windows to manage and execute Playlists
- Project's call tree : t
- Tracker ATS
- Build dashboard
- Open in system explorer
- Open terminal
- Project's builder : To build and package a project and to build an image from Agilitest
- Maintenance : To check the ats scripts in your project and to refresh
- Saved searches
Create a new component

From the project menu, in the side bar, you can create a new component, Agilitest provides a selection of different types of component.
Configuration menu

At the bottom of the side bar there is a button to modify some menus displayed in the editor.

You can change where you want these buttons to be displayed on your editor.
Agilitest settings

Agilitest settings allows you to:
- Generate error reporting
- Parameter the lanugage of the Agilitest editor (french or english)
- Configure ATS
- Configure Jenkins
- To connect to Agilitest enterprise
- To connect Mobile Station or Git accounts
Help Menu
You can find the help button at the top right of the editor.

This will open a window with various help links.

From the help menu you have access to:
- Agilitest archive download link
- Mobile Station download links (Windows and MacOS)
- Player ATSV download link
- Various resources to support your path on Agilitest (documentation, videos, webdrivers, etc…)
External tools menu

You can improve your experience by adding tools that communicate directly with Agilitest. Among those tools there are:
- ATS OpenCV
- Apache Maven project management
- FlaUInspect
- Jenkins server
- SAP
Project explorer

The project explorer is a structure tree that lists all the projects and elements they are composed of.
It allows you to have a global view of a project and to bring global modifications as well as to limit the step-by-step method.
From the project explorer’s menu you can modify the view of the tree.

To know more, you can consult the documentation about the project explorer.
Channels management
Channel management menu is a prerequisite before you start editing a test, it is a central element of Agilitest and that will facilitate the test creation and maintenance.

In this channel management menu you have access to:
- The Capture tool button
- The Close button to close the current channel
- The Play button to play the script
- The Next button to play an action and the following one
- The Parameters button to set up the execution management
Script’s variables
The script’s variable menu allows you to create and visualize all the variables that are used in a script.

This is to avoid having the variables in the script’s core that is only made for actions.

Scripts management
Actions menu
The Agilitest actions menu is central and allows you to manually declare all the possible actions in a test script.

In this menu you will find all the agiles actions that are used during a test. It was made to secure the most compatibility between all the devices supported by Agilitest.
This menu is also used to manage different channels used in a test.
Script editor
Agilitest script editor represents a big part of the editor. It shows the actions you can execute on your tests. The editor will propose graphical interpretations of the actions that will be performed on your script. The ATS format is a textual format that will describe all its actions.

This section of the editor is designed to allow the reuse of components: copy of the actions or elements on which they act on or with subscript creation.
The actions display only shows the principale actions, but all cases can be managed in sub-menu.

Script header
The script header menu is used to manage a set of metadata linked to a test, like execution suite for example.
To have access to the script header, open a script and click on the “Script’s header data” button

You can visualize the ATS script corresponding to your test.

💡 Tip
This can be useful to copy the information from the script’s header and send it by email or add it to a comment in your bug tracking tool.
You can also have access to the Java code which once it is compiled will allow the execution of the tests.

🔸 Warning
ATS and Java scripts cannot be edited directly in the editor.
To return to the script editor, click on the "Actions" button


