Published versions and upcoming versions of Agilitest

• Possibility to import Python libraries into the ‘libs’ directory of an ATS project

‍

• Recall script

• From now on, the list of default imports will be as follows for the Python “evaluate” variable:
  
  • import os; import sys; import platform; import glob; import math; import cmath; import decimal; import fractions; import statistics; import random; import numbers; import string; import re; import textwrap; import difflib; import unicodedata; import base64; import binascii; import html; import csv; import json; import urllib.parse; import ipaddress; import uuid; import time; import datetime; import calendar; import collections; import operator; import heapq; import bisect; import hashlib; import hmac; import secrets; import pprint; import fnmatch; import encodings

‍

• Mobile Station update

• Start channel - Documentation links
  
  • All the start channel actions have a link to the documentation to learn more about how to use each one and about the options that can be applied to them

‍

• Drag and Drop of URL into the action’s list of a script
  
  • Dragging and dropping an URL from the address bar of a browser (Chrome, Firefox, etc…) will create a “Go to URL” action in the list of actions

‍

• Blocking multiple updates
  
  • A blocking system is implemented for Agilitest updates if an update is already in progress

‍

• CTRL-T, CTRL-N and CTRL-Shift shortcuts are replaced by equivalent Window actions 
  
  • The keyboard shortcuts CTRL-T, CTRL-N and CTRL-Shift no longer exist, they have been replaced by the equivalent existing functions 
  • CTRL-Shift (browser’s parameters) corresponds to the Go to URL action
  • CTRL-A , CTRL-C, CTRL-V are still working

‍

• Search by script
  
  • A search by script button is added in the project explorer.This action has an improved keyword and filter search process (action, author, description)

‍

• Capture tool - Statistics‍
  
  • In some cases, there may have been a blockage in the statistics that required a restart of Agilitest

‍

• Reports generation‍
  
  • Errors in generating a report could occur due to an error in retrieving the results of a single test

‍

‍

• File transfer - File upload
  
  • New action that allows you to download files without going through the standard save component on Windows, Linux, or macOS, but by retrieving the URL of the downloaded file with the hyperlink component in a web page

‍

• Moving directories with file renaming and sub-script calls
  
  • Several script directories can be moved in the project explorer. Moving them will automatically rename sub-script calls or references to the use of these scripts and sub-scripts

‍

• Project output directory added to the ATS script's special values
  
  • Option to use the default output directory for the current project. This allows you to save files and access files generated during test executions. This is a special value that can be retrieved from the special values menu in a text entry (ATS script values > Project path)

‍

• Priority element by default
  
  • When an action is performed on the “root” element of a web application, the action will attempt to be performed primarily on the element that is the default focus in the application

‍

• Use of space in uploads
  
  • During an upload, if there were spaces in the path of the file to be uploaded, this caused an error in the upload action

‍

• Passwords management with the “p data” file
  
  • When the “pdata” file (old password storage mode) was not deleted, password management with the new mode did not work correctly

‍

• “textContent” recovery with Selenium
  
  • In some cases, retrieving the textContent property with Selenium could add non-printable characters that prevented values from being compared or elements from being searched for by property

‍

• Languages management in Docker containers‍
  
  • The environnement variable “LANG” is addedwith the name of the language in the Docker command line (-e LANG=en)

‍

• Plugins management on Firefox‍
  
  • Option to declare plugins in the ats properties file so that the Firefox browser automatically installs these plugins on startup ‍
  • https://gitlab.com/actiontestscript/ats-core#customize-ats-on-host-machine

• OpenCV on macOS‍
  
  • This feature previously existed only for Windows and has now been implemented for macOS. It allows you to perform checks and obtain status information on the number of shapes detected in a video on the application being tested (examples: checking that a video is not black or frozen, and that it does indeed contain graphic content)

‍

• Improved ergonomics and visuals for importing scripts and script packages‍
  
  • It is possible to import directories from the project explorer. The script import also offers the option to import either as a package or as a script in the directory and automatically add subdirectories

‍

• Automatic update on macOS‍
  
  • The availability of a new update is checked when Agilitest is launched on macOS. It is possible to accept the automatic update from Firefox

‍

• Editor: drag drop scripts from report to playlist scripts
  
  • From the test report, scripts can be dragged into the playlist management section of the Agilitest editor

‍

• Reporting: more details in ActionCallscript‍
  
  • In the report, callscript actions have more details: the table passed as a parameter, the list of parameters, the tree structure of the element passed as a parameter, as well as more details in case of failures in the execution of the action (if the sub-script, data files, or elements are not found)

‍

• Check on remote files exists used by ActionCallscript‍
  
  • When a remote file is passed as a parameter to a callscript action, the remote file is checked before the action is executed

‍

• Use of variables research in JSON and CSV ‍
  
  • Searching for data files if a project variable or environment variable is used in one of these files

‍

• Fix 'check' property on react check boxes that return wrong boolean value‍
  
  • Check boxes in “react” applications did not return the good “checked” value of the property 

• Fix use of 'about:...' url with Go to URL action and firefox‍
  
  • Use of the go to URL “about:...” in Firefox which allows you to access browser elements configuration settings

• Loading data file paths and ATS scripts after renaming files or directories in Windows with the same name but different case‍
  
  • In some cases, when the paths of an ats project files was renamed with the same name but a difference in the upper and lower case on the characters, the editor could not open the script in the project repository

‍

‍

• Ability to load Chromium extensions with remote, local, or directory files
  
  • Ability to load extensions for Chromium-based browsers by defining the paths to the extension. You can define either a path to a crx file or to the entire extension directory. In addition, you can define extensions either in the ats properties file or in the startup arguments of a Chromium-based browser channel
  • https://gitlab.com/actiontestscript/ats-core#customize-ats-on-host-machine

‍

• Temurin 21 by default downloaded through Agilitest
  
  • The version 21 of JDK Temurin is downloaded by default 
  • https://adoptium.net/fr/temurin/releases

‍

• Firefox pluggins management 
  
  • Possibility to define a list of authorized plugins during test execution (for Firefox only)
  • https://gitlab.com/actiontestscript/ats-core#customize-ats-on-host-machine

‍

• Docker and Podman desktop images download progress
  
  • Ability to view the progress of a Docker image download when using an Agilitest Linux Desktop container (Docker Desktop and Podman Desktop)

‍

• Add time zone selector for desktop containers
  
  • Ability to set the time zone when starting an Agilitest Linux Desktop container

‍

• Watermark for ATSV_HTML player
  
  • Option to set a watermark for the “ATSV_HTML player” visual report

‍

• Timezone parameter in command line
  
  • When launching an execution with a Docker image, you can define the time zone of the test execution

‍

• Running container counter
  
  • Display of the running containers in the toolbar

‍

• Download select multiple JDK distribution
  
  • Now you can choose between several available JDK distributions from the Agilitest settings tab

‍

• Check error in playlist test selection (null script)
  
  • In some cases, if the user moved or renamed scripts outside of Agilitest, Playlists that used these scripts were no longer synchronized and errors could occur. Now, it is possible to view these errors and manually clean up these faulty scripts.

‍

• Update UI for import script and package in execution Playlists
  
  • Improved ergonomics and visuals for importing scripts and script packages

‍

• Real time management of the Playlists
  
  • Changes to playlists are saved in real time, there is no need to press the save button anymore

‍

• Display of packages in a Playlist
  
  • In the playlist selection, the scripts in a package are displayed after each package. It is not possible to rearrange the order in which scripts are executed between scripts and packages

‍

• Element selector rectangle more reliable when elements are inside iFrames 
  
  • In certain web applications and specific cases, elements displayed in iFrames were not displayed correctly in execution reports

‍

• Generate ATSV_HTML in docker container
  
  • ATSV_HTML runs in a Docker container

‍

• Concatenation of nested variables 
  
  • Concatenating different types of variables did not work in all cases, for example in the property file where you can concatenate a prefix, an environment variable, and a parameter variable

‍

• Catch enter text error when dialog box does not exist
  
  • When text was entered into a dialog box that had not appeared, the error was not captured during test execution

‍

• Use of a lower than character in variable in editor
  
  • The “<” character was not visible in certain types of actions in the editor

‍

• Support of JDK 25 in editor
  
  • JDK 25 is now officially supported in the Agilitest editor and in test execution

‍

• ATS velocity in environment variable
  
  • The ATS_VELOCITY environment variable was not taken into account when launching an ATS test from the command line

‍

• Use of a lower than “<” character in scripts variables
  
  • Script variable values appeared empty when this character was used

‍

• Management of backslash “\” character in properties files
  
  • The “\” character caused problems when used in properties files

‍

• Default values of ”\” and “#” characters
  
  • Correction of the characters “\” and “#” used in the default values of parameters and environment variables

‍

• ATSV clean= true or false
  
  • The ATSV_CLEAN=true environment variable can now be used during test execution to clean up ATSV files at the end of an execution. The “clean-atsv” command-line command will always take precedence over the environment variable

‍

• Ability to pass parameters to a script launched from the command line
  
  • In the ATS launcher, you can add another parameter called “parameters” followed by one or more parameters separated by commas. These parameters will be used in a script when a script is called. 
  • Example: java AtsLauncher.java ats-report=3 suite.var=chrome script=AtsDemoScript parameters=param1,param2,param3
    

‍

• Historization of search item in the editor
  
  • Searches for elements are reusable

‍

• Possiblity to click on a group TAG of a script
  
  • Opens the selected group in the groups panel

‍

• ATS properties: Management of the algorithm for calculating resilience and wait times during execution
  
  • One of the basic principles of ATS operations is to use this algorithm. Its variables have not changed much in recent years, so we decided to overhaul this algorithm and the expectation values. Developments and material improvements in runtime hardware and networks have made this overhaul possible
  • 3 levels of algorithm execution have been implemented:
  • The “aggressive” level: Provides faster execution; the “normal” level: Provides standard execution based on several years of testing experience; the “safe” level: Provides more secure times and algorithms.
  • This is achieved by passing a parameter in the command line when executing a test. In the ATS launcher, we use the “velocity” parameter, while in the Java command line, we use “ats-velocity” and “ATS_VELOCITY” as environment variables (the command line takes precedence over all other variables).
  • Example with the ATS launcher: java AtsLauncher.java ats-report=3 suite.var=chrome velocity=agressive script=AtsDemoScript

• Report summary: Inside execution report the header was not visible when using a font color or double quotes in the summarie’s code

‍

• Code error Javascript, Python
  
  • When a JavaScript or Python subscript had a syntax error or was not executable, the script did not stop at that error. Now, an error in the code stops execution

‍