v3.6 (2025-12-03)

Welcome to AIVA news for version 3.6. You may have noticed that we skipped the last release and newsletter. We discovered a critical bug just before the planned release. This time though, a new AIVA is here with quite a few improvements to show you.

Let’s start with the most obvious one: AIVA now has a Getting Started page! You can find the first two tutorials there, with more coming soon. Once we go public with AIVA, this page will be accessible even before logging in, as will an About page with contact info, legal documents etc.

While we’re on the topic of going public: we’re hard at work on the preparations, and the public pages are just one symptom of that. Aside from all the back-end deployment work, we are also preparing a way for an anonymous guest to try out the basic functionality of AIVA before they even sign up for an account. And once they do decide to sign up, they will be presented with a choice of authentication providers: Microsoft, Google, GitHub and eventually Apple, as we want to make it really simple to just start using AIVA, and not complicate the customer journey with making yet another password.

On a related note, you have just (or will very soon) received an invitation to a new instance of AIVA (with your existing data preserved), to which you will no longer have a special login (like today, “Tenant123user” etc.), but instead you will be logging in with whatever user account you are used to using (single sign-on). You will also be able to invite others to your tenant, who will then have access to the same environment and same scenarios.

To help us understand how users discover and use our system, we have integrated some analytics tools. With that comes more pervasive usage of cookies and with that, the unfortunately necessary cookie acceptance banner.

Localization of elements on the target webpage is a key function of AIVA, and it works well in most cases. Users can now report an issue when AIVA did not correctly locate some element. This helps us improve the procedure and make AIVA better. The user needs to keep in mind that this shares the screenshot and metadata to our engineers for further investigation.

AIVA can truly learn from its past mistakes. With a lot of dynamic content on modern web pages, even the best localization algorithm can get into trouble. What seemed to be a static part of the page and thus a good anchor point, all of a sudden changed two days later, when the content was replaced. The test fails and AIVA asks you to heal the test by showing her the button again. From this release, this is no longer an isolated correction. When designing the new strategy for localization, AIVA will consider all of its past attempts and failures, to not fall for the same unreliable dynamic content.

User testing of the Edit mode area has provided us with plenty of valuable insights. We observed how users work with individual features in this area and editing via re-recording proved to be the most critical. On the one hand, this is the way users expect to edit a test in many cases, but on the other hand, it is not easy for users to figure out exactly how this functionality works in its entirety, and some of the terminology in the UI also proved to be unclear. Due to the high perceived value of this method of test editing, we have decided to repeat user testing at least once more after incorporating the improvements.

Based on user feedback, we added an option to delete any test step while recording a test. Users need to be cautious as it can cause the test not to follow up properly. Together with Edit mode, this increment gives users more control over the test itself.

You can now replay the remaining steps in rerecording. This is yet another of our efforts to save every second of your time. In a past release we’ve added a now very popular feature, which allows you to add or replace any steps wherever in your test cases. However, to check whether the new version of the test is valid, you had to go through the hoops of saving it and executing it from the very start. Now, you can execute just the remaining steps directly from the re-recording context, allowing you to make any corrections right away, if necessary.

Gateways allow you to test web apps that are only reachable on your local network, be it your localhost or a local server. We’ve now extended this important feature to also natively support Mac OS and Linux distros.

Patience tells AIVA how long it should wait for a desired state of your tested app. For text assert function, you can find this setting in the advanced options section. Until now, the function did not consider that not only the correct text, but also the enclosing element may take its time to appear and position itself on the page. We realized that and told AIVA to be more considerate in the future.

AIVA can now type Czech (and many other) diacritics and non-Latin characters. Yes, nothing can stop you now from testing your app with a Bulgarian locale set up.

Coming soon:

• As mentioned above, limited anonymous guest usage by new users
• Feedback buttons in AIVA for users to send us questions or issue reports directly from the app
• “About AIVA” page
• Usability improvements of edit mode based on user testing

Finally, an updated roadmap:

And this is all from us this year. Thanks for your eagerness to be part of the revolution in test automation. Thanks for all the feedback and support.

Merry Christmas and happy testing in 2026