Allure TestOps 25.1.1

The release notes documentation page can be found here: https://docs.qameta.io/allure-testops/release-notes/#03-march-2025--allure-testops-2511

Webhooks in Allure TestOps

Added the ability to send information about events from Allure TestOps projects to third-party systems using webhooks. For example, you can set up integration with your work messenger and receive messages about the beginning and completion of launches, detected defects or creation of new test plans.

Code generation for test cases automation

Added code generation: the ability to generate code for automated test cases in supported programming languages directly in the Allure TestOps interface.

New operators in filters

Expanded filter capabilities in the Test cases section ("New test case tree" feature flag):

• Added the Partial Match (OR) and Exact Match (AND) operators, which provide the ability to filter test cases by partial or full match of selected attribute values.
• Added the Does Not Contain (NOT) operator, which provides the ability to filter test cases by excluding selected attribute values.
• Added the No value switch, which provides the ability to filter test cases by empty attribute values. Filtering by empty values works in combination with the Partial Match operator.

Redesigned Launches section

Updated the Launches section: it is now available without the feature flag and allows you to work more efficiently with launches and test results.

User menu

Replaced the user profile page with the user menu, which combines all user settings. The user menu allows you to:

• view and edit profile information — name, avatar, email, password, and interface language are displayed in the sidebar, not on the separate page;
• create API tokens to configure integrations with Allure TestOps via the API;
• enable feature flags and preview Allure TestOps beta features;
• select color themes for the workspace and the navigation sidebar.

The Administration section has moved to the breadcrumb navigation. To access it, click the project name and select Administration from the menu that appears.

Global cleanup rules

Added a predefined set of global cleanup rules to new Allure TestOps instances. This applies to all Allure TestOps cloud instances, as well as Allure TestOps server instances deployed for the first time (without created projects).

Encryption algorithm

In the Allure TestOps settings, added the ability to select the encryption algorithm used when saving objects to the S3-compatible storage.

Version history feature flag

Added version history in test cases as beta feature ("Version history in test cases" feature flag): advanced versioning with the ability to store, compare and restore test case versions.

To activate beta features, follow the Activating beta features instruction.

Improvements

• Enhanced the capabilities of the new test case tree ("New test case tree" feature flag):
  • Added the ability to change the status of a test case in the tree, without having to open the test case for editing.
  • Added a Select all button to select all test cases in the tree.
  • Adjusted the sorting logic of test cases: now the order of categories changes only when you select alphabetical sorting, all other sorting types affect test cases only.
• Updated the navigation within Allure TestOps:
  • Added a button to return from the settings of an individual integration to the general list of integrations in the project settings.
  • Improved transitions between projects via the breadcrumb navigation: when switching to another project, the user is taken to the section that was open in the previous project before switching.
  • Expanded the breadcrumb navigation: now it displays the name of the open test case, defect, and shared step.
  • Improved the navigation in the project settings: in the breadcrumb navigation for the project settings added a separate drop-down list with subsections, in the navigation sidebar added two click areas for the project settings section (expand/open).
• Improved the user experience in the Launches -> Tree section:
  • Optimized the view of parameters in test results: now parameters in a test scenario are hidden by default.
  • Added the ability to paste images from the clipboard into the test results scenario.
• Added the ability to save filters in the Launches section.
• Adjusted the logic of displaying issues from the issue tracker when importing test cases: now the imported test case displays links to issues directly linked to this test case.
• Updated the TMS sync settings: now TMS sync will be automatically disabled in case of access problems. In the settings you can specify an email, to which the notification will be sent when TMS sync is disabled.
• Added forced termination of a user session if their global role changes. After user signs in, a new session with the current permissions will start.
• Increased the click area for opening attachments in test case scenarios. Attachments are now expanded when you click their title.
• Added the ability to view test case scenarios in already open test case cards when the Allure TestOps instance is unavailable.
• Optimized the connections in database tables that contain user account information to speed up processing of complex queries.
• Improved the handling of time zone data in dashboards and its display on widgets, and reduced the length of intervals to further break down data in widgets.
• Optimized the logic for selecting interface language when user signs in for the first time: now at first visit Allure TestOps uses the language set in the user's browser.
• Added other minor updates and fixes to the Allure TestOps to optimize it and improve user experience.

Bug Fixes

• Fixed the issue where after removing an AQL query from the widget, the wrong number of test cases was displayed and query validation error occurred.
• Fixed the issue that occurred when exporting launch results to CSV format.
• Fixed incorrect iFrame behavior in Jira that caused launch information to be displayed outside of the iFrame.
• Optimized building the test case trees to speed up tree processing.
• Fixed the error that caused elements with data to be displayed incorrectly in the Launches section.
• Fixed the error that caused the test case tree to reload after user changed status, test layer, or cloned test cases.
• Fixed the mapping of SortObject properties in Swagger, SortObject properties now match the described schema.
• Fixed the error where parameters in scenario steps were incorrectly displayed in the test results.
• Fixed the error where the test case ID was not displayed after renaming the test case in the test case tree.
• Fixed the issue with the automated tests progress bar not displaying correctly in a launch.
• Fixed the issue where the update time was displayed incorrectly after user updated a saved filter.
• Fixed the issue that caused test result artifacts not being removed when using the API for instance or project cleanup.
• Fixed the issue that caused content search to fail for shared steps.
• Fixed the behavior of api/testresult/bulk/resolve endpoint where the endpoint allowed to change the status of automated tests. Now the endpoint correctly rejects requests to change parameters of automated tests and applies changes to manual tests only.
• Fixed vulnerabilities in dependencies, updated org.springframework.boot to version 3.4.2.
• Optimized data insertion and update operations to prevent database locking when processing queries.
• Fixed the issue that prevented users with viewing and commenting permissions from adding comments in test cases.
• Replaced the database connection pool for uploading test results using allurectl: now the uploader pool is used instead of the main pool.
• Fixed the incorrect display of AQL fields in the “Automation Trend” widget: now the fields Filter by test cases and Filter by launches are not displayed when creating and customizing the widget.The release notes documentation page.The release notes documentation page.

0 Votes