v4.7 (2026-04-21)
Welcome to AIVA news for version 4.7. This time, we are presenting one new, long-awaited feature, and a few minor improvements.
New feature: GitHub integration
With this release, we are introducing the first of our planned integrations of AIVA with CI/CD pipelines. Perhaps unsurprisingly, we have started with GitHub, although its competitor, GitLab, is coming very soon afterwards, too.
What is this good for? Let’s assume you have a pipeline in GitHub that builds and deploys your app after any commit. Now, you can easily add a step that runs your test set in AIVA, too, and you will see the results right there in GitHub. (Plus, you can also trigger the test workflow manually in GitHub, or configure it to run on a schedule.)
You can find the integration steps described in the How to execute AIVA tests from a CI/CD pipeline section.
Minor usability improvements
During our user testing sessions, we frequently noticed the issue with accessibility of AIVA documentation from the product. You can now find the documentation linked in the header next to your personal information. We also reorganized the documentation content into meaningful sections and added more descriptive How-to pages.
Another usability issue that repeatedly came up during user testing was the way the processing of individual recorded steps was visualized. Our users (including some of you) expected that they would have to wait until the previous step had been processed efore recording the next one. However, that is not the case, and users were unnecessarily delayed by waiting for processing of each step due to AIVA’s misleading visual communication. The animation showing that the recorded step is still being processed in the background is now much more subtle, and we believe it will help users better understand what is happening in the app.
In this release, you can also notice some improvements in the Batch runner. The tests that failed to execute are marked with a separate icon, which also appears in the overall status of the batch. Also, the tests using a Gateway are now marked with its respective icon. When creating a new batch and overriding a variable, AIVA will show you the number of tests the variable is used in. All these changes were driven by early adopters that joined a user testing session with us.
You can also find a new tutorial describing the setup of gateways for local testing on the Getting Started page.
Coming soon
- GitLab integration
- Editing click/hover location