Skip to main content

v5.2 (2026-07-14)

Welcome to AIVA news for version 5.2. This release brings a new feature – extracting Authentication modules from tests – along with a set of noteworthy bugfixes. We’re also including an updated roadmap at the end.

Also: new mascot! Yay!

Authentication modules from your existing tests

You can now extract the first steps of an existing test into a reusable Authentication module, right from edit mode. You select the range of steps (starting from the very first one), give the module a name, and AIVA turns those steps into a standalone authentication flow that your test then references. This means less duplicated setup across tests and one place to maintain your login flow.

Extract module button in a test's edit mode

Selecting the steps and naming the new Authentication module

In a test’s edit mode, you can also now replace one authentication module with another.

Replacing a test's authentication module with another

CI/CD integration improvements

We’ve polished running AIVA test batches from your CI/CD pipeline. The AIVA runner (our GitHub Action) now ships as tagged, versioned releases, so you can pin a specific version instead of always tracking the latest – handy for security-conscious teams. While a batch runs, the pipeline now reports regular progress instead of going silent, and if something goes wrong – a batch that can’t start, or results that can’t be fetched – you get a clear, meaningful error report in GitHub and GitLab rather than an opaque failure.

Notable bugfixes

  • Adding an assert while editing a test could sometimes fail with an “unexpected error” – this no longer happens.
  • You now stay logged in to AIVA much longer. The login session persists for 30 days, instead of asking you to re-authenticate after about a day.
  • The gateway drop-down in the re-recording dialog is usable with the mouse again – it previously flashed and closed immediately – and your test’s default gateway is now pre-selected.
  • When switching from a passed test result to a failed one, the Issues and Details tabs now show up correctly, without needing a page refresh.

Coming soon

  • Generic modules – reusable modules you can use anywhere in a test, unlike Authentication modules, which always sit at the beginning of a test
  • Notifications in scheduler
  • User choice of how elements in tables are localized (by content, or by position)

Roadmap update

AIVA roadmap as of 2026-07-14

Thank you for your continued support and feedback!