v4.5 (2026-04-08)
Welcome to AIVA news for version 4.5. We hope you enjoyed your Easter break and have come back refreshed and eager to automate more tests.
The new features this time are rather minor but still hopefully a noticeable improvement to how you work with AIVA.
More speedup
As promised last time, we weren’t done with making test recordings faster. This time, we’ve implemented a pool of standby agents so that in most cases, test recording will start faster than ever before. In our tests, we’ve achieved 50-70% better recording startup times, down to approximately 3 seconds.
Parallel execution of test batches
If you select parallel execution mode when creating a new batch of tests, you can now configure how many tests can run simultaneously. This gives you more control of how AIVA resources are used and can help prevent situations where a large batch of tests eats up all the resources for an extensive period of time.
Visual asserts with a single click
Visual asserts were already deeply explored in the last newsletter. In this version, we added an option to just click an element with the Assert image tool (instead of drawing a box around it), and it automatically locates a button, an icon or an input. The assertion is then added to the test steps and can be edited, if needed. This behavior now matches the text assertion tool. We are commencing user testing for the whole feature of image assertion, so more improvements will be made after that.
Coming soon
- Easy integration with CI/CD pipelines in GitHub and GitLab
- Editing click location in edit mode
- Improved documentation and its discoverability
- User editable comments on test results
- Change of S3 provider – You may have noticed recently that AIVA has unfortunately been encountering some issues, for example with saving recorded tests. We have identified the root cause as instability of the cloud provider we are using for S3 cloud data storage. What initially looked like a temporary outage has turned out to be a bigger issue, and so we are now transitioning to using a different cloud provider. We apologize for the disruptions this may have caused.