Skip to main content

v3.3 (2025-10-22)

Welcome to another edition of AIVA news, this time for version 3.3. You can also find the updated roadmap at the end.

In Edit mode, you can now record new steps in the middle of a test and then connect them to pre-existing steps.
A big part of test automation is test maintenance. It usually is a tedious and repetitive process that nobody (including us) likes doing. Therefore, with AIVA, we are striving to be smart about it and save actions where possible. For situations where assisted healing is not enough, you can re-record part of the test. From this release, you can even replace just the faulty steps and leave the rest of the test as is. AIVA will do its best to connect the original parts with the newly recorded steps. You just need to make sure that your last inserted step and the first original step are on the same page, literally. 😉
Based on early feedback, we are also adding an option to run the rest of the original steps as part of the recording process, to save you even more clicks.

Screenshot of re-recording a part of a test in AIVA

You can now schedule multiple tests to be executed as a batch. You select the test set using labels, choose whether they should be executed in parallel or in sequence, and optionally override some variables. AIVA then puts the test set in a queue and executes it as agents become available. This functionality is also available via the API. Batches defined from AIVA can be reused as template to run them again. At this stage, it is not yet possible to schedule the execution for a specific time or set a regularly repeating schedule, but this is on our roadmap.

We have also used this new functionality in the API endpoint for executing a single test. This is completely transparent for the end user and nothing changes in the way you use the API – except that you should no longer encounter the error for when AIVA runs out of available agents, because the test will simply be queued in that case.

Screenshot of running a new batch in AIVA Screenshot of a running batch in AIVA

Further adjustments regarding gateways are ahead of us, as recent usability testing has shown that AIVA should be more helpful to users and communicate instructions more clearly, especially during the initial gateway setup. In addition, we are also considering extending full support for this functionality to platforms other than Windows due to known limitations that have already become apparent during testing with our Mac users.

Most important bugfixes:

  • Healing of assert text action now contains multiple related images.
  • If the user enters an invalid URL during recording, they are informed of this, and they can redirect somewhere else.
  • When using auth. module in recording, the Home action now leads to the actual home URL of that module.

Coming soon:

  • Replay remaining steps during re-recording
  • User signup
  • Feedback/issue reporting directly from AIVA
  • Welcome/landing page
  • AIVA load testing and performance optimization

Here is the updated roadmap:

AIVA roadmap as of 2025-10-22

Thank you for your continued support and feedback!