Published versions and upcoming versions of Agilitest
This changelog presents you with the list of latest developments, additions and bug fixes in Agilitest.
Upcoming version :
Version :
3.0.5
Expected publication date:
27/1/2026
Expected publication date is not known
- Added :
- Possibility to import Python libraries into the ‘libs’ directory of an ATS project
- Libraries can be added to an ATS project by copying the libraries to the project's libs directory.
- Split reports
- You can choose to display only tests that have passed or failed in a separate report according to the following usage:
- ats-split-report : Used in the command line with the values 0,1 or 2
- 0 : Only the principal report is generated (Default behaviour)
- 1 : Only “fail” and “pass” reports are generated
- 2 : Both the principal and “fail” and “pass” reports are generated
- 0 : Only the principal report is generated (Default behaviour)
- ATS_SPLIT_REPORT : Used as an environment variable with the same value as seen above
- You can choose to display only tests that have passed or failed in a separate report according to the following usage:
- Comments of summary type are back in the report Summary
- In the Summary report in HTML, it is possible for each script to additionally display report summaries in relation to comment actions.
- Search by script button in the project explorer
- Formatting of the hours in the variables
- Possibility to import Python libraries into the ‘libs’ directory of an ATS project
- Changed :
- Evolution :
- Reworking of Python and JavaScript math evaluations
- Python and JavaScript mathematical evaluations did not perform optimally for use in the editor when multiple variables or sub-script calls were used, etc. Now, RUST is used for these variable transformations because it is much more efficient and faster for this type of operation
- The functionality on Python has been limited in order to improve performance, with only certain library imports being taken into account by default (see description below)
- From now on, the list of default imports will be as follows for the Python “evaluate” variable
- import os, sys, platform, calendar, statistics, heapq, bisect, string; from string import Formatter
- For more information, read the documentation: www.agilitest.com/documentation/variables-usage-in-agilitest#python
- MobileStation update
- Improving the reliability of mobile capture
- Formatting HTML comments in the editor
- Possibility of having a WYSIWYG editor for the comments action in test scenarios
- Reworking of Python and JavaScript math evaluations
- Fixed :
- Update of libs repository when a library is added to the project
- When a .jar file was added to this directory from the editor, the view was not refreshed and the new .jar did not appear.
- MobileStation : Visibility of iOS devices on macOS 26
- Update of libs repository when a library is added to the project
Changelog :
Version :
3.0.0
Publication date:
24/9/2025
- Added :
- 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
- ATSV clean= true or false
- Changed :
- Evolution :
- 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
- ATS properties: Management of the algorithm for calculating resilience and wait times during execution
- Fixed :
- 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
Version :
2.9.9
Publication date:
17/9/2025
- Added :
- Reports: Duration by action type
- Now all actions in a test case have their action times displayed in reports. There are 7 different types of actions, each with their own action time
- Search for "used by" scripts and data files: Displaying “potential uses”
- These potential uses correspond to variable names. This will display a list of scripts that could potentially be called with a variable, as opposed to scripts that are definitely called by name
- Search for items for the file upload action to view all items relevant to this action
- Search for all elements that can accept the upload action. This search is used to identify invisible elements that cannot be dragged and dropped but exist on the page (input elements of type file)
- Soap header recovery
- Header properties recovery when capturing elements from a SOAP API call
- Property variables : Variabilization of the property file’s name
- Previously, only the key could be variabilized, but now the property file name can also be variabilized using environment variables, project variables, script variables, and parameters
- Cleaning of dangling images on container engines (Docker and Podman)
- Dangling images correspond to intermediate images needed to build other images
- Reports: Duration by action type
- Changed :
- Evolution :
- Java JDK 24 and Temurin 21 version support
- Agilitest regularly updates its components and Java in order to avoid any security issues and vulnerabilities. Currently, Agilitest is compatible with versions 21 to 24 of Open JDK and version 21 of Temurin
- Temurin is a secure, high-performance Java runtime environment that has been rigorously tested for stability and optimized for transparent operation in a variety of environments https://adoptium.net/temurin
- Reports: Group management
- Modification of graphics to be more consistent with the version in the editor. More visible and understandable reading of groups with the display of the group name, trigram, color, and description
- Memory management improvment
- Improves memory object management to enable better memory release after closing scripts and data files
- "Used by" pop modification
- Standardization of element usage search items
- Choice of whether to use a local image in containers (Podman and Docker)
- Check "local image" in configuration tu use only a local image, which is an image from the machine and not from the container remote repository
- Java JDK 24 and Temurin 21 version support
- Fixed :
- Capture tool: Scroll bar fixed when a lot of elements appear in a webpage
- The parent window of the captured element could exceed the height of the screen, so a maximum height was defined to view this list
- Using a local container image to run Linux Ubuntu desktop
- When using local image for Linux Ubuntu "desktop" the container would not start (see added section for local images)
- ATSV_HTML environment variable, link in the report
- When the system environment variable ATSV_HTML=true was set, this generated the animated ATSV_HTML report but did not create the link to this report in the execution report
- Capture tool: Scroll bar fixed when a lot of elements appear in a webpage
Version :
2.9.8
Publication date:
3/9/2025
- Added :
- New file upload action
- File selection : Possibility to copy a file into asset repository
- ATS Project properties can now build Linux Docker image
- Execution duration for these actions : callscript, channel start and channel close
- Drag and drop of an ATS script into Slack or text editor
- More launching functionnalities Selenium Grid
- https://gitlab.com/actiontestscript/ats-core#selenium-grid
- Changed :
- Evolution :
- Possibility to drag and drop all types of scripts and data files in the explorer
- Switch window action : A window without a name returns empty
- Before, a switch action without a name returned an URL. If you have any relevant tests, please search by URL
- ATSV HTML5 file is not generated by default with the ATSLauncher anymore
- Animated reports set false by default for each execution type
- Execution duration can be hidden in the reports
- Concatenation of execution results
- This concatenate multiple runtime metadata files generating single xml and html reports with information from all selected runtime files.
- https://gitlab.com/actiontestscript/ats-core#report-concatenation
- This concatenate multiple runtime metadata files generating single xml and html reports with information from all selected runtime files.
- New HMI for separators in conditions (clarification of labels)
- Search for usage of passwords and project variables
- Display of the capture source code in HTML page (this feature could block some cases)
- "language-pack-fr" added in Docker image "actiontestscript/linux-base"
- Fixed :
- In ATS search scripts: the creation date of the scripts displays the correct date
- Multi-try fixed for switch and close web windows
- Validation report regenerated when option is selected
- Report : Taking into account searches for elements with criteria in HTML format
- Report : Fixed password masking in actions with API data
Version :
2.9.7
Publication date:
27/6/2025
- Added :
- Minimize explorer display
- You can minimize the left panel in the explorer to only show the script editor
- Network capture and HAR files
- The Network capture action is used to set up a recorder to evaluate network traffic during ATS test execution.
- More info: www.agilitest.com/documentation/network-activity
- Ability to add or remove a watermark in an execution report
- Minimize explorer display
- Changed :
- Evolution :
- Test percentage in reports
- In the reports the percentage of the passed or failed tests are calculated with 2 decimals for tests with large volume
- Copied callscript action with the same name prevented
- When copying a sub-script call action, if the script name is that of the current script, the action will be commented to indicate that the script has not been pasted, as it cannot call itself
- Define string delimiters with quotes
- Possibility of using quotes instead of single quotes in Java script conditions
- Capture tool regex
- Possiblity to replace spaces with \s* instead of .*
- Test percentage in reports
- Fixed :
Version :
2.9.6
Publication date:
6/6/2025
- Added :
- Changed :
- Evolution :
- Pop up user ID to enter an username and an email
- Agilitest will manage the difference between users using a same ID system with this data
- Subscript called with a drag and drop
- Pop up user ID to enter an username and an email
- Fixed :
- Use Javascript in a mouse click action
- Loading data files
- Saved project variables

