Skip to main content

v3.8 (2026-01-14)

First of all, let us wish you the best in the new year, we hope you are well rested and looking forward to all that is to come this year. Welcome to AIVA news for version 3.8, the first of this year.

Following up on the Getting Started page we shared last time, we've just published a new blog post: “The Testing Recursion”. It’s about how we test AIVA with AIVA. You’ll find the link in the “Did you know?” section—it’s a fun (and slightly meta) look behind the curtain.

We’ve also added a new About AIVA page. It includes the necessary legal details, plus—probably more exciting right now—a Subscription Plans section outlining our proposed tiers and pricing.

Please keep in mind that everything there (including the prices) is still preliminary and subject to change. We’re actively collecting feedback and will especially value your thoughts as part of the early group before we lock anything in. What do you think—any initial reactions to the plans? Note that all of you, our valued Early Adopters, will keep the existing access equivalent to the Team subscription at no cost for at least 6 months from now.

Screenshot of AIVA subscription plans

AIVA now suggests you to add an Assert text action at the end of a module or a test, if there isn’t any. It is a good practice to always finish a test or module with an assertion that the System Under Test is in an expected state. Previously, AIVA forced the user to add an assertion at the end of a module, but we ultimately made it just a suggestion.

Screenshot of AIVA suggesting user to add an Assert step

Based on your feedback, we improved the way how to connect steps in re-recording. Now you can individually select which steps to keep and which to remove using checkboxes at each step.

Screenshot of original steps in test re-recording

Before we dive into more advanced forms of scheduling and running tests, we continue to improve the functionality of the batch runner. Through user testing, we have discovered that we need to improve the visibility of which tests are selected in the batch and will be run. Upcoming improvements may, for example, include better integration of the batch runner with the Tests page and a clearer communication of labels filtering. Other points from the category of improving communication with users are also explaining limits on the number of parallel tests and notifying the use of variable overrides within batches. We expect these future enhancements to make batch creation easier, as well as improving the interpretation of batch results and investigating potential issues.

We added a few sections into our documentation, most notably How to... and Known Limitations. Feel free to read through and give us feedback in case of any inconsistencies.

Most significant bugfixes:

  • Multiple screenshots are now available for updating a text assert area
  • Test names can be copied easily from the tests table using a copy icon

Coming soon:

  • User signup – anybody will be able to sign up to get access to AIVA after it is released
  • Feedback buttons in AIVA for users to send us questions or issue reports directly from the app
  • Usability improvements of edit mode based on user testing

Thank you for your continued support and feedback!