If you want to know more about Agilitest, you will probably want to discover its user interface, and try to understand how it works.
We encourage you to watch the screenshots below, then take the plunge and download the software to your computer!
Here is the Agilitest editor editing an automated test case. Each step of the test is represented by a line on the right side of the software.
Just drag and drop actions (top bar) to add steps to the test. Each of these lines also corresponds to a line of ATS code generated in the background.
The test was launched, and we also see the Chrome channel that was opened on the page https://web2.0calc.fr.
A sub-script was used to describe the calculator program once, and set it using a CSV file located in the test working directory then data / data_calcul.csv.
Each column of the CSV file corresponds to a parameter to be used in the test scenario. Each line of the CSV file corresponds to an iteration of the test.
The CSV file for setting the test scenario is opened here. Looking at this file, we guess that the columns will be exploited as follows:
Column 1: Functional commentary
Column 2: first computation operand
Column 3: calculation operation (addition, multiplication, …)
Column 4: second calculation operand
Column 5: expected result for comparison
Several channels can be opened in the same test case. In this test, we start a Chrome channel, then Firefox, Windows Native Calculator and finally an Android Application Calculator. Several technologies can be tested within the same test scenario to cover the entire functional scope of an application.
The Agilitest locator is the feature that allows you to easily and quickly select which buttons and areas of the application to be clicked, or for which keyboard input is required.
A special feature of Agilitest is to allow you to check the classes and identifiers of each element described in the test. You can respect the structure of the application and its data, and keep the development logic when creating the test.
When talking about the multi-channel aspect of Agilitest, here is an example very commonly encountered: the modal window for selecting a local file to send it to the web application. Agilitest will be able to activate the “Open” button even if it is not apart of the web application.
The Agilitest locator also works with desktop applications, but of course, URL, CSS class or HTML tag are not applicable in that case: the structure of the application is decrypted by Agilitest to allow you to recognize the elements by their attributes exposed by the application to Windows.
As a global multichannel tool, the Agilitest locator works the same way with mobile applications. You can identify the buttons and text boxes of the application by hovering over them with the mouse and checking the desired attributes. Agilitest recognizes the composition of a typical structure of an apk application written in Java for Android, with its elements, sub-elements and attributes.
Opening a mobile channel (Android) requires first to select the mobile application on which to run the test. Any application can be tested, as standard, event the applications delivered with the Android operating system!
Agilitest can be used to produce automated tests on SOAP or JSON webservices. The data received by the webservice is displayed in an internal Agilitest internal viewer highlighting the logic and the data tree. You’ll then benefit from the same behaviour to produce tests as if it was a web application.
If webservices usually only return textual data, it is quite possible to display as comments in Agilitest the images whose addresses are provided by the webservice. This makes it possible to visually check that the received data is compliant.
After creating a test case, it can be ran using the Agilitest editor, or directly from the command line. The test run consists of a Java program execution. You’ll then directly see in the Agilitest editor what will happen while launching your tests using a continuous integration system.
Agilitest can generate runtime files to replay all the tests of a project meeting certain criteria on any continuous integration system supporting the TestNG standard.
Agilitest allows you to activate components using graphical recognition. This makes it possible to manage situations for which the graphical display is essential, or simply when the other technologies are inoperative (for example web canvases).
Agilitest works with Neoload to variabilize test cases in order to achieve performance shots. It is essential to vary the tests so that the infrastructure operates in real conditions without the results being affected by caching, or a lock on a database record written concurrently.