Version: 2.2.2
Release date: 01 Oct 2020

Minimum requirements:

  • — CPU: 4 cores server grade w/ virtualisation support and clock rate 2.2 gHz or higher
  • — RAM: 6GB
  • — Net: 100 Mbit/s
  • — HDD: min 10 GB

Recommended Requirements:

  • — CPU: 8 cores server grade w/ virtualisation support and clock rate 2.2 gHz or higher
  • — RAM: 12 GB
  • — Network: 1 Gbit/s
  • — SSD: min 100 GB

About version

Test IT introduces the new version of Aquila 2.2.2, which has new features for working with automated software testing, and allows you to get an improved user experience. We have added the feature to track and analyze launches of automated tests in a single interface, it was created a new section «Launch story». Aquila also expanded integration options with the Jira bug tracker, and introduced features for scaling the system.

Test automation

The “launch history” module allows to track all launches of autotests, even if they are not from test plans, for example, night execution of autotests.

A convenient form for launching autotests displays statistics and a list of autotests with the results and reasons for each crash. Tests are structured by namespace and class in the source code.

In Test IT you can now analyze the results of the causes for the autotest crashes! The new release features autotest results card, where the user can examine autotests’ artifacts (error logs, screenshots, attached files, crash steps, history of passes, and other information), leave a comment, link to the defect and choose one of the possible causes of the error: AutoTest, product, or infrastructure.

For users

Visual highlighting of test changes. In the log you can now navigate even more conveniently through your test versions, checklists or shared steps.

Improved integration with JIRA. The new release features automatic data attachment when adding a link during test execution. The link is automatically added to both the result and the requirement issue in JIRA.

We have also implemented end-to-end integration when adding a link to an issue in Jira in the test card!

For administrators

In the new version admins now can create multiple WebApi replications using the same database within a single Test IT.

The Aquila release features the ability to replicate and distribute the load between multiple RabbitMQ consumers.

Now you can configure the use of external services db, elasticsearch, minio, avatars.db, avatars.minio, license-service, authdb, RabbitMQ, and influxdb.

It is now possible to connect two Test IT instances to the same data sources.

Added the ability to add a single group or subdirectory from AD.

Added the ability to synchronize multiple Test IT instances using the public API.

Enhanced public API functions

Version 2.2.2 enables users to export test cases using the API. When you export tests, you can choose the project, specific sections of the project or specific tests to export. The user receives the export file in a .JSON file format.

The new release also allows to import test cases using the API. When importing tests, the structure of sections in the project, names, descriptions of tests, system and user attributes, preconditions and postconditions of tests and sections, shared steps and links are saved.

When you re-import tests, they are matched (even if the WI was deleted) and updated to the new version with an entry in the change log.

When importing tests, the history of execution is saved within the TestIT where we import cases. The history of execution is not transferred and is not overwritten during import / export.