Index

Release Notes

We strongly advise upgrading your Allure TestOps instance only to the releases listed in this very release notes document.

Until further notice please update your docker-compose.yaml for RabbitMQ image as follows:

image: rabbitmq:3.8-management

instead of

image: rabbitmq:management

See in details here

Starting from the version 3.185.0 we’ll forbid running Allure TestOps without the following parameters added to the configuration. This configuration parameter is to be added to both - uaa and report services.

For docker-compose and Kubernetes deployment: ALLURE_CRYPTO_PASSWORD, for packages deployment allure.crypto.password

For more details please refer to the following article.

3 March 2022 - Allure TestOps 3.193.0

πŸ”₯ New Features

  • We’ve added capability for the users to request their password reset from the log-in page.

πŸ”¬ Improvements

  • We’ve added capability to supply test cases’ lifecycle status to the test results when exporting a launch’s information to the CSV file.
  • We’ve made the password reset by an admin more consistent with the action (menu items were updated and the message to a user was updated to reflect the action was made).
  • We’ve added an evaluation for super user creation. Now, it is not possible to create a super user without a name and a password.
  • We’ve updated email templates for password update and reset workflows.
  • We’ve improved test case patch API method including its proper documentation (check /swagger-ui.html page).

🐞 Bug Fixes

  • We’ve fixed an error when PDF export of a launch contained incorrect dates (the date and time of the generated report was used instead of the date and time of a launch).
  • We’ve fixed a bug which was allowing a user to see profile details of other users by substitution of a profile id in the address string.
  • We’ve fixed a bug preventing launch’s export to CSV. When the end user was selecting the ID of a test for the export, the latter was failing with the error 400.
  • We’ve fixed a bug which was breaking the layout of the Users page in the administration section in a case when there was a user with no authorities assigned to them. Now, the page is being rendered correctly.
  • We’ve fixed a minor bug in the UI which was preventing the update of the latest step’s status in the manual test during the execution and was causing a bit of annoyance.
before after

18 February 2022 - Allure TestOps 3.192.2

πŸ”¬ Improvements

  • We’ve added search capability to Administration > Users.
  • We’ve made AllureID assignment for CSV import always optional. This is a rare case when AllureID is present in CSV files for import, so to avoid user mistakes we’ve made this always skipped by default.
  • We’ve added support for AWS STS.

🐞 Bug Fixes

  • We’ve fixed a UI bug with the pagination buttons.

if you see this write to support.qameta.io

  • We’ve fixed an UI bug when sub-steps were collapsing when a parent step received focus in edit mode.

14 February 2022 - Allure TestOps 3.191.0

πŸ”¬ Improvements

  • We’ve added pagination in Administration > Users section to improve the performance on huge users lists.
  • We’ve done small UX improvement for meta data sorting in the UI:
    • Tags are now sorted by their value alphabetically
    • Custom fields are sorted alphabetically based on CF name (key)
    • Environments are sorted alphabetically based on Env name (key)

🐞 Bug Fixes

  • We’ve fixed a bug in launch status trend widget data preparation caused dashboard crash in 3.190.0 - 3.190.3.

8 February 2022 - Allure TestOps 3.190.4

4 February 2022 - Allure TestOps 3.190.3

2 February 2022 - Allure TestOps 3.190.2

1 February 2022 - Allure TestOps 3.190.1
26 January 2022 - Allure TestOps 3.190.0

This release requires IDE plug-in to be upgraded to release 3.16.2.

This release requires TestOps plug-in for Jenkins to be upgraded to release 3.28.2.

πŸ”¬ Improvements

  • We’ve updated the sorting of the entities liked to a defect – test cases, test results, launches are now ordered by their IDs.
  • We’ve added a capability allowing usage of several S3 to store tests’ artifacts. This is to override limitations of such solutions like Ceph.
  • We’ve enhanced the access rights management. From now on, even the users with ROLE_ADMIN must be explicitly added to a project to be able to upload the tests’ results. This prevents human errors and is now consistent with the access rights model on a project level.
  • (3.190.4) We’ve implemented wrong data error processing in widgets, so the wrong data received by a widget won’t break the application.
  • (3.190.4) We’ve implemented proper processing of attachments added to fixtures (setup & tear down blocks). Now the attachments from fixtures are being added to Attachments tab of a test.

🐞 Bug Fixes

  • We’ve fixed the navigation between input fields in modal windows of steps when adding various types of attachments. Now, the end users can navigate between those fields using Tab again.
  • We’ve fixed incorrect processing of files removal tasks for cases when files have been already deleted. Now, if a file does not exist, we’ll consider the deletion operation as competed and won’t create the task again.
  • We’ve fixed import from CSV files with long strings in columns. Now, import for test cases with long strings (longer than 4096 chars) in fields should work.
  • We’ve fixed a bug that was preventing an end user from creation a table attachment to a step in a scenario. Now the button Create table works properly.
  • (3.190.1) We’ve fixed a bug preventing the end users from deleting links from test cases.
  • (3.190.1) We’ve applied a workaround for launching the manual test cases with long (longer than 255 chars) parameters’ values. Tests will run, but parameters will be cropped in the launches.
  • (3.190.1) We’ve fixed an error preventing saving the environment information for launches created manually by upload of test results.
  • (3.190.2) We’ve fixed slow queries for launches stats gathering.
  • (3.190.3) We’ve fixed the processing of Enter key press in modal window for text attachment creation. Due to an error the key press was ignored when creating a new attach.
  • (3.190.3) We’ve fixed the scenario step width in edit mode, it was half cut in edit mode, but now it’s fixed.
  • (3.190.4) We’ve fixed an error preventing the update of a test’s status in the tests tree after this test’s execution was completed and test was marked as Passed or Failed. if you see this write to support.qameta.io

18 January 2022 - Allure TestOps 3.189.2

This release requires IDE plug-in to be upgraded to release 3.16.2.

This release requires TestOps plug-in for Jenkins to be upgraded to release 3.28.2.

It’s recommended to upgrade to 3.190.0 and skip this release.

17 January 2022 - Allure TestOps 3.189.0

πŸ”₯ New Features

  • We’ve added capability for all users to update their passwords.

🐞 Bug Fixes

  • We’ve fixed the loading for Custom Fields values options in CF suggest. Due to an error the suggestion list was limited by 20 records and it was not possible to select anything behind this number. Now, it’s working as expected.
  • We’ve fixed an error that was allowing to initiate launch with several env parameters having the same name. Not anymore.
  • We’ve fixed the processing of zip-files content type on Windows machines. It was necessary to manually update content type before uploading the test results archives. Now, Allure TestOps accepts the content type detected by browser when running on Windows OS.

Before if you see this write to support.qameta.io

Now if you see this write to support.qameta.io

  • (3.189.1) We’ve fixed a bug that was preventing an end user to change their password.

  • (3.189.1) We’ve fixed a bug preventing the sync of defect life cycle with linked bug tracker’s issue life cycle.

    if you see this write to support.qameta.io

  • (3.189.2) We’ve fixed main page redirect to swagger pages.

29 December 2021 - Allure TestOps 3.188.3

22 December 2021 - Allure TestOps 3.188.1

This release requires PostgreSQL 11+.

Please be reminded, we’ll discontinue the support of all versions prior 11 (inclusive) by the end of 2021.

This release of Allure TestOps won’t start without these changes in your configuration.

πŸ”₯ New Features

  • We’ve added test case change log feature preview. Now, the changes made to test cases will be logged and could be reviewed in new Change log section. if you see this write to support.qameta.io

    • this feature is now DOES NOT track the changes of:
      • ❌ relations,
      • ❌ mutes,
      • ❌ links,
      • ❌ scenario,
      • ❌ attachments,
      • ❌ parameters

πŸ”¬ Improvements

  • (3.188.3) We’ve improved the test cases import operations from CSV. Now when importing test cases with existing AllureID, Allure TestOps won’t reset the attributes for which no mapping is selected.
    • A use case: if you want to update certain attribute(s) for some existing test cases, you need to map AllureID from CSV to AllureID in Allure TestOps, then map only needed attribute, then import test cases, and only mapped attribute will be updated in the existing test cases, and the rest of the attributes of an existing test case will remain untouched.

🐞 Bug Fixes

  • (3.188.1) We’ve fixed a bug introduced in 3.188.0 preventing the deletion of a project. Now it’s fixed.
  • (3.188.1) We’ve fixed a problem in Retries widget of a Launch overview page causing Out Of Memory failure in case of huge (500K+) amount of retries within a single launch.
    • we also added pagination for the said widget to improve its usability.
  • (3.188.3) We’ve fixed a bug which was causing the deletion of attachments from test cases’ steps for the actions Allure TestOps creates change log for.
  • (3.188.3) We’ve fixed a bug introduced in 3.188.2 which was causing the system’s crash under high load.

10 December 2021 - Allure TestOps 3.187.1

This release cannot be applied to Allure TestOps with Postgres v. 9. If you have Postgres version 9 in your infrastructure, please upgrade at least to Postgres v.12 first.
This release of Allure TestOps won’t start without these changes in your configuration.

πŸš€ New Features

  • We’ve added capability to update test cases from the CSV import if the source CSV contains AllureID. So, now, you can export test cases to CSV, make a lot of changes and then import data from CSV again and Allure TestOps will update existing test cases with the changes you’ve done in the file.

πŸ”¬ Improvements

  • We’ve refactored the view of avatars’ colors a bit.
  • We’ve added the export of a full name for test cases forth both – test cases and test results.
  • We’ve added the license consumption information to the UI.
  • (3.187.1) We’ve refactored roles and access for the users with different roles.

🐞 Bug Fixes

  • We’ve fixed an issue when it was not possible to run a test if parameter’s value was longer than 255 chars. Now it’s possible.
  • We’ve fixed invalid relation directions when creating clones of test cases.
  • We’ve fixed an issue with the creation of Jira issues from Allure TestOps, now the reporter information is taken from the integration information, i.e. the account used for the integration will be used as Reporter by Jira.
  • We’ve fixed an issue when the assignees’ information for manual test cases was ignored by the system.
  • We’ve fixed an issue with the selection of users from users suggest, when it was not possible to select anything except first 10 suggests.
  • We’ve fixed global problems with the pagination for the users with read only rights. This issue affected the functionality of Jira plug-ins as well. Now, the pagination should work same way for all the users in the system.
  • We’ve fixed an issue that was preventing the creation of test cases on XRay Cloud side. Now, all the stuff is pretty cool.

πŸ”₯ Security

  • (3.187.1) We’ve fixed an error allowing an end user to upgrade their privileges in the system via API.

22 November 2021 - Allure TestOps 3.186.0

This release cannot be applied to Allure TestOps with Postgres v. 9. If you have Postgres version 9 in your infrastructure, please upgrade at least to Postgres v.12 first.
This release of Allure TestOps won’t start without these changes in your configuration.

πŸš€ New Features

  • We’ve added support for JSON format logging.
  • We’ve added an integration with XRay Cloud.

πŸ”¬ Improvements

  • We’ve done various enhancements on the FE part related to the spacing, shadows, styles of elements.
  • We’ve restyled sider menu.
  • We’ve fixed the validation of the entered license.
  • We’ve replaced default users’ avatars with placeholders.
  • We’ve added validations for dashboards widgets, so the unacceptable values won’t pass to the settings.

🐞 Bug Fixes

  • We’ve fixed some bugs with the processing of the test results.
  • We’ve fixed pageable parameters parsing for widgets. So the widgets with the pagination work as expected again.
  • We’ve fixed the manual categories assignment for manually failed tests from the bulk actions of the test results. Ok now.
  • We’ve fixed an error when after the deletion of last element on last page of paged list the end user saw empty page instead of the pagination controls.
  • We’ve fixed error when server was sending response 200 for the request of the progress for non-existing launch ID. Not anymore.

2 November 2021 - Allure TestOps 3.185.3

This release cannot be applied to Allure TestOps with Postgres v. 9. If you have Postgres version 9 in your infrastructure, please upgrade at least to Postgres v.12 first.
This release of Allure TestOps won’t start without these changes in your configuration.

πŸ”¬ Improvements

  • We’ve added mandatory properties validation, and Allure TestOps won’t start without ALLURE_CRYPTO_PASSWORD and ALLURE_ENDPOINT added to your configuration, see details here.
  • We’ve improved report service’s performance for attachments linking procedures.
  • (3.185.1) We’ve added capability to change the default roles for different log-in types. This will allow registering all new users e.g. as ROLE_AUDITOR and license consumption will be under control.
  • (3.185.2) We’ve implemented simple services discovery for k8s.

🐞 Bug Fixes

  • We’ve fixed an error in iframe needed for the integration with Jira.
  • (3.185.1) We’ve fixed an error when it was not possible to set default log-in type as saml2.
  • (3.185.1) We’ve fixed a problem with the issues creation in the cloud version of Jira when creating the issues from Allure TestOps side.
  • (3.185.1) We’ve fixed a problem with the strings trimming leading to the numerous records related to errors for database insert operations (ERROR: new row for relation "test_tag" violates check constraint "test_tag_name_check"). Now, the issue is fixed.
  • (3.185.3) We’ve fixed k8s configuration parameters.

18 October 2021 - Allure TestOps 3.184.3

This release cannot be applied to Allure TestOps with Postgres v. 9. If you have Postgres version 9 in your infrastructure, please upgrade at least to Postgres v.12 first.
If you are going to upgrade from a release older than 3.177.2 please apply the migration procedure for 3.177.2 The migration procedure is described here.
Please update your configuration when upgrading to 3.184.X as described here

πŸš€ New Features

  • We’ve introduced new widgets for launches statistics.
    • Last launch status Pie chart, which output you can adjust using launches related AQL if you see this write to support.qameta.io
    • Launches trend by launches, which output you can adjust using launches related AQL if you see this write to support.qameta.io

πŸ”¬ Improvements

  • We’ve improved pagination for long lists.
  • We’ve redesigned the context menus. These had unnecessary inactive scroll bars which are gone now.
  • We’ve removed menu icons’ names tooltips, so now they do not generate any visual noise in the UI.
  • We’ve fixed test cases sorting by ID. Now, the feature uses AllureID for sorting of the tests cases.
  • We’ve made configuration parameter ALLURE_CRYPTO_PASSWORD (for packages it will be allure.crypto.password) a mandatory one; this one is to be added to report and uaa to encrypt secrets stored in the database. Parameter will become a mandatory one starting from 3.185.x release. Parameter’s absence will cause Allure TestOps’s emergency stop during the start attempt. The value of the parameter could be a random string with length more or equal to 64 characters. Loosing this parameter will lead to the inability of using the secrets stored in the database.
  • We’ve made parameter ALLURE_ENDPOINT (allure.endpoint) a mandatory one for both – report and uaa services. This will be needed of the references to Allure TestOps instance.

🐞 Bug Fixes

  • We’ve fixed a bug with integration links where issues’ IDs were displayed as /null, now this issue is fixed and Allure will create correct links.
  • We’ve fixed the modal window for the comparison of a manual scenario vs. the automated test scenario received from the test results.
  • We’ve fixed the extremely precise display of the fractional part in the tests success rate widget. Now the fractional part is limited by 2 digits.
  • We’ve fixed a UI bug which was appearing after the zoom of a tree’s branch and switching to another tree. Now, you won’t see the infinite page load.
  • We’ve fixed broken processing of web-hooks from Jira cloud. Now the web-hooks is being processed correctly and defects’ life cycle will be updated accordingly to the life cycle of the linked issue in Jira.
  • We’ve fixed a UI bug which was appearing when cloning single test case from test case’s menu.
  • We’ve fixed Youtrack’s issues suggest (it was not working!).
  • We’ve fixed errors processing in to send correct response to a client.
  • We’ve fixed the erroneous transformation of the strings containing consecutive digits and full stops to a URL address in the scenarios steps.
  • We’ve fixed the issue with eternal refresh of the test cases page after clearing of a boolean Muted filter.
  • (3.184.2) We’ve fixed a bug when creating a new grouping in a test case tree. Groups weren’t created and there was eternal progress indicator.
  • (3.184.3) We’ve fixed grouping rename from the tree. It was not possible to update the name of a grouping using UI.
  • (3.184.3) We’ve fixed the underlying elements count in the groupings. Before the fix users saw NaN which was not really informative.
  • (3.184.3) We’ve fixed the displaying of Allure TestOps launches in Jira plug-in. Now the Launches are back.

πŸ”₯ Security

  • We’ve fixed a security bug when read-only users were able to alter global-scoped entities such as issues and trackers.
  • We’ve added the fix for CVE-2020-8908
  • We’ve added the fix for CVE-2020-13936

29 September 2021 - Allure TestOps 3.183.0

This release cannot be applied to Allure TestOps with Postgres v. 9. If you have Postgres version 9 in your infrastructure, please upgrade at least to Postgres v.12 first.
If you are going to upgrade from a release older than 3.177.2 please apply the migration procedure for 3.177.2 The migration procedure is described here.

πŸš€ New Features

  • We’ve added support for passing of the mandatory fields when creating issues in Jira issue tracker.
  • We’ve added API to request of the job status and to cancel build job on Gitlab side. Feature itself will be available in next releases.

πŸ”¬ Improvements

  • We’ve added a new configuration option for blob remove tasks (allure.scheduler.cleaner.blob.batchsize/ALLURE_SCHEDULER_CLEANER_BLOB_BATCHSIZE) in report service to manage the batch size. If your tests have a lot of attachments, you can increase this parameter to remove more than default 5000 attachments per 5 minutes.
  • We’ve improved a lot of stuff in UI. Enjoy new shiny design.

🐞 Bug Fixes

  • We’ve fixed potential deadlocks when processing the retries.
  • We’ve fixed the processing of broken regular expressions for matching of the categories, so even if the regexp is not correct, the test results still will be processed correctly.

22 September 2021 - Allure TestOps 3.182.0

This release cannot be applied to Allure TestOps with Postgres v. 9. If you have Postgres version 9 in your infrastructure, please upgrade at least to Postgres v.12 first.
If you are going to upgrade from a release older than 3.177.2 please apply the migration procedure for 3.177.2 The migration procedure is described here.

πŸš€ New Features

  • We’ve added new API to request job status and cancel job on CI side. In next releases Allure TestOps will be able to request job status on CI side and stop the jobs’ execution.
  • We’ve added support for hidden and masked params. Wait for the updates in test frameworks integrations.
  • We’ve added support of launch export and creation of issue for the integration with TargetProcess.

πŸ”¬ Improvements

  • We’ve enhanced the notifications the end user sees from the system.
  • We’ve enhanced the performance of launches environment filter.
  • We’ve redesigned the pagination for lists.
  • We’ve enhanced the filtering of the projects in the main UI page - All projects
  • We’ve updated the look and feel of the buttons and icons in Allure TestOps UI.
  • We’ve updated the design of the sider menu.
  • We’ve added auto expand for a selected group in the tree of errors.

🐞 Bug Fixes

  • We’ve fixed the relations for tests cloning. Relation linked to the source and target tests was incorrect. Now it’s back to the normal.
  • We’ve fixed wrong behaviour of the menu items while accessing them from keyboard. It wasn’t possible to enter a menu’s list of items and select an item from keyboard. Now it is working.
  • We’ve fixed integration paths for TeamCity to avoid breaking the integration for some types of TeamCity CI deployment.
  • We’ve fixed the link for retries of a test.

19 August 2021 - Allure TestOps 3.181.5

This release cannot be applied to Allure TestOps with Postgres v. 9. If you have Postgres version 9 in your infrastructure, please upgrade to Postgres v.12 first.
If you are going to upgrade from a release older than 3.177.2 please apply the migration procedure for 3.177.2 The migration procedure is described here.

πŸš€ New Features

  • We’ve added a bulk move action for test cases. Now, you can select test cases and move them to other project.

if you see this write to support.qameta.io

  • We’ve added a capability to copy a launch.
  • We’ve added TargetProcess integration as an issue tracker.
  • We’ve added the capability to manage license via UI and from now on, the license for Allure TestOps is stored in its database. Check it out in Administration > License (you need to have ROLE_ADMIN to do that).
  • We’ve added the capability to create a copy of finished launch. Now you can take a launch with a set of the test cases and run the same set of test cases again. It’s also planned to copy the name and environment information in future, so stay tuned!

πŸ”¬ Improvements

  • We’ve improved errors from back end processing in gateway service. Now, service will report proper status codes from the back end services.
  • We’ve added the granularity for certain widgets types, now you can see the data per day, per week and per month.
  • We’ve redesigned the pagination of the lists.
  • We’ve enhanced the styles of the charts.
  • We’ve enhanced the styles of the widgets for better look and readability.
  • We’ve redesigned the look of Test case’s history page.
  • We’ve improved the view of the images attached to scenario’s steps, now small images aren’t enlarged to fit the width of a step an look much better.
  • We’ve improved the rendering of the All projects tab, from now on, you won’t see blinking You have no projects if you have some projects in fact.
  • We’ve added local XML schema for old version of XCResults, so Allure TestOps won’t need any Internet access to process these.
  • We’ve added settings and processing of authentication and authorization attributes from LDAP when they are returned using different letters case. Now the parameters are transformed to lower case, thus there will be no weird stuff with the permissions for the end users.

🐞 Bug Fixes

  • We’ve fixed the webhook processing thanks to Jira users. Now the life cycle of defects is synced with the life cycle of an issue in a issue tracker.
  • We’ve fixed the missing scenario compare button, now it’s back and the automation will go on.
  • We’ve fixed the merging of the launches. Now, the older test results will be overwritten by a newer test result and they will be sent to Retries.
  • We’ve fixed the statistics for the projects list. Now, you’ll only see the active test cases.
  • We’ve fixed an error when a usual end user was able to see the list of all (even private) projects registered in the system without being added to them. They weren’t to access them, though. Now, users are able to see only the projects where they are explicitly added as team members.
  • We’ve fixed a bug when the most recent launch where a defect is found was displayed incorrectly (we were showing first launch instead of the recent)
  • We’ve fixed the faulty behaviour of UI on the hot keys events (they were erasing the content of the steps), now things got back to normal.
  • We’ve fixed the cases when some of end users could have duplicated test results or even duplicated jobs creation for tests rerun.
  • We’ve fixed a situation when project owners and admins weren’t able to delete filters created by other administrators.
  • We’ve fixed test results processing for labels with empty values ({ “name”: “label_name”, “value”: “" }), now the tests results will be processed correctly and appear in the launches.

Important Changes

  • We’ve discontinued the support of Postgres database ver. 9 in our product.

22 July 2021 - Allure TestOps 3.179.2

If you are going to upgrade from a release older than 3.177.2 please refer to the migration procedure for 3.177.2 The migration procedure is described here.

πŸ”¬ Improvements

  • We’ve enhanced the test results upload operation
  • We’ve introduced new filter type for Launches. Now, you can filter out the launches based on relation to a Job.
  • We’ve tweaked UI so the filters look better.
  • We’ve enhanced the filtering of tests in a Launch, now you can filter your test by ID, Name, Issue
  • We’ve added tests parameters examples to test case CSV export.
  • We’ve dramatically improved the processing of test results.

🐞 Bug Fixes

  • We’ve fixed the UI behaviour when deleting a launch with an enabled filter. Before the fix the filter was reset, now the filter remains and filtering is active.

19 July 2021 - Allure TestOps 3.178.0

If you are going to upgrade from a release older than 3.177.2 please refer to the migration procedure for 3.177.2 The migration procedure is described here.

πŸš€ New Features

  • We’ve redesigned the main page - project page, and now the admins will be really happy, so now you have the page with 3 tabs:
    • 1st tab contains all the projects where you are the owner.
    • 2nd tab contains all projects you marked as favourite.
    • 3rd tab contains all projects to which you have the access.

if you see this write to support.qameta.io

πŸ”¬ Improvements

  • We’ve added createdAfter/createdBefore filtering options to the history of a test case (Test cases => test case => History => Filters).
  • We’ve added tooltips with useful information in Graph tab of a launch.

if you see this write to support.qameta.io

  • We’ve fixed permissions of Read only users that were allowing them to change test cases scenarios, now this is not allowed.
  • We’ve fixed the parsing of test results from outdated versions of Allure framework. Tests from outdated FW test results were marked as Unknown state instead of state in the result.

🐞 Bug Fixes

  • We’ve fixed an error that caused the stack trace was included to each parent step in case of several nested steps in a test case scenario.

if you see this write to support.qameta.io

  • We’ve fixed Launches’ timeline error that was breaking whole layout.

if you see this write to support.qameta.io

  • We’ve fixed possible loss of the tags during the migration.

8 July 2021 - Allure TestOps 3.177.2 - requires migration procedure - please read carefully

This release requires migration procedure

Release 3.177.2 requires migration to new configuration and cannot be started without it.

The migration procedure is described here.

πŸš€ New Features

  • We’ve added the support of GitHub run.
  • We’ve added the support of Circle CI run.

πŸ”¬ Improvements

  • We’ve updated the PDF report, and from now on you won’t see retries there.
  • We’ve improved the DB operations for text fixture results link.
  • We’ve improved the DB operations for tags migration.
  • We’ve added the transition to filtered launch tree when clicking on the defect in the launch’s overview tab.
  • We’ve added endless scrolling for loadable lists.

🐞 Bug Fixes

  • We’ve fixed custom fields suggestions. There was a small mistake allowing the suggest to be taken from wrong fields. Now, it’s working as expected.
  • We’ve fixed the bulk remove members from a test case.
  • We’ve fixed the alignment of buttons in Launches.

18 June 2021 - Allure TestOps 3.176.4

πŸš€ New Features

  • We’ve added +New defect button in Defects section of a project. Now, you can create defects from Defects section. Works like a charm!

    if you see this write to support.qameta.io

  • We’ve added new filter by status to test case’s history. It works in Test cases section and in test results area of a launch.

    if you see this write to support.qameta.io

πŸ”¬ Improvements

  • We’ve added trimming of the strings provided in tags, so now smoke and smoke (there is space after the word) will be the same and there will be no same-same-but-different looking tags.

  • We’ve improved defects matching – defect matchers will be reapplied on launch’s reopen.

  • We’ve added button to force reapply the defects matcher in open launch.

    if you see this write to support.qameta.io

  • We’ve removed Storage stats at all as we weren’t able to trust this data.

  • We’ve renamed Storage section to Clean up policies.

  • We’ve added an option to include parameters in tc last status widget. Now, each parameterized test could be counted in the test results separately for each set of parameters.

🐞 Bug Fixes

  • We’ve fixed an error when end user was not able to create an issue in Azure issue tracker.
  • We’ve fixed an issue with selection of a key from Issue tracker.
  • We’ve fixed and issue with the selection of TMS system when linking custom fields to TMS.

11 June 2021 - Allure TestOps 3.175.0

πŸš€ New Features

  • We’ve added new API function to sync two test cases. Now, you can copy everything from one existing test case to other existing test case.

πŸ”¬ Improvements

  • We’ve added capability to access all active elements in Allure TestOps UI by pressing Tab.
  • We’ve improved the focused element rendering.

if you see this write to support.qameta.io

  • We’ve added pagination for Top test cases widget.
  • We’ve done refactoring for test cases import/export via CSV files.
  • We’ve improved the clickability (is there such a word?) of check-boxes in the test cases tree. Now, the area responding to the mouse click is bigger and it’s easier to switch the state of a check-box.
  • We’ve improved the suggestions while linking defects. Now, Open defects will appear on top of suggested defects list and then defects in the suggested list will be ordered by creation date, i.e. most recently created ones will be on the top of the list.
  • We’ve updated the ordering of the launches for a defect in Defects section. Now, the most recent launch will be on top of the list.
  • We’ve updated the ordering of the test cases for a defect in Defects section. Now, the test cases are ordered alphabetically based on their names.
  • We’ve updated the ordering of the test results for a defect in Defects section. Now, the most recent test result will be on top of the list.

if you see this write to support.qameta.io

  • We’ve allowed empty steps in a test case scenario.
  • We’ve added separate button to import test cases.

if you see this write to support.qameta.io

  • We’ve added separate button to import test cases.

if you see this write to support.qameta.io

🐞 Bug Fixes

  • We’ve fixed the rendering of a test case type (manual/automated) in Jira issue’s test cases information block. A bit earlier any test case was shown as manual and now each type is being rendered correctly.
  • We’ve fixed content type detection for CSV files on Windows machines. Now, content type for CSV files is detected as text/csv instead of application/vnd.ms-excel.
  • We’ve fixed preview for CSV import. Now import shows any specified row number content from source CSV file.
  • We’ve fixed parsing of the steps in CSV files while importing test cases from third-party TMSs.
  • We’ve fixed the drag’n’drop of test cases in the test cases tree.
  • We’ve fixed the detection of latest defect appearance in launches, now you will see the real latest appearance of a defect. Previously Last found was showing first appearance of a defect instead of the latest one. Not anymore.
  • We’ve fixed the usage of RQL in filters.
  • We’ve fixed the deletion of the parameters in a test case. Now, the parameters from a test case can be deleted completely.
  • We’ve fixed the test case’s layout breaking due to a long tag presence.
  • We’ve fixed a funny problem where the keyword in a step of a test case scanario (that thing [in square brackets]) would become invisible until the user pressed Submit.

πŸ”¬ Improvements

  • We’ve added test plans filtering by their names.
  • We’ve added live update for Pie chart diagram in Overview tab a ongoing launch, so it’ll show you the actual state based on the received test results.

if you see this write to support.qameta.io

  • For mutually exclusive filtering criteria (test cases Type and Launches CI filter options) we’ve added radio buttons instead of check-boxes.

if you see this write to support.qameta.io if you see this write to support.qameta.io

  • We’ve added the auto assignment of a test in a launch to the current user if they made some actions to steps in the test. Test will be automatically assigned to current user if…
    • “mark as passed” or “marked as passed” clicked
    • “pass previous” clicked
    • “resolve step” clicked
    • an attachment added

if you see this write to support.qameta.io

🐞 Bug Fixes

  • we’ve fixed the max limit for the automatic closure of launches, now it is really limited by 365 days.
  • we’ve fixed an error (white screen) that was caused by incorrect processing of a step without text, now the step with no text is rendered correctly without errors.

17 May 2021 - Allure TestOps 3.173.0

πŸš€ New Features

  • We’ve added GitLab’s webhook support.
  • We’ve added parameters generator for test cases. Now, if you provide possible values for parameterized test cases, Allure TestOps will generate all possible combinations of these parameters for you.

πŸ”¬ Improvements

  • We’ve adjusted font size for Allure TestOps UI.

  • We’ve added a new font for UI.

  • We’ve added status update for tests cases in the tree, recently the status of a test was updated only after the tree refresh, now, if you update a test case from its menu, the status will be updated everywhere - in the test and in the tree.

  • We’ve replaced username filter with member filter.

  • We’ve updated a lot of dependencies, it is not really visible for the end users, but still cool and beneficial for them.

    ALT TEXT

🐞 Bug Fixes

  • We’ve fixed annoying issue when after the deletion of the last test case in the tree you were observing a blank page. From now on, you’ll see an empty tree as anyone could expect in this case.

ALT TEXT

  • We’ve fixed the integration with Bamboo related to the variables and selection of the branch.

23 Apr 2021 - Allure TestOps 3.172.0

πŸš€ New Features

Wait for it…

πŸ”¬ Improvements

  • We’ve supported increased step’s description length. Step’s description length was unfairly limited by 250 characters. From now on, the users will have more freedom.
  • We’ve added some missing indexes again. This is a good thing, you have to trust us.
  • Defects search improved. We added searching for a defect by a linked issue ID. Also, new default sorting mode shows open defects first.
  • We’ve added branded layout in the authorization form.

🐞 Bug Fixes

  • We’ve fixed attachments names encoding. Sometimes, adding attachments with symbols caused mojibake. For example, the symbol " turned into something like %[email protected]. The problem is fixed, and the users have the freedom to name attachments!
  • We’ve fixed select scrolling in modal windows. It was quite rare issue, so you hardly faced it. But still we’ve reproduced and fixed it.
  • We’ve fixed link’s text selection. Text selection in links now works as we expected.

18 Apr 2021 - Allure TestOps 3.171.0

πŸš€ New Features

  • We’ve added new feature for Jira Cloud webhook support. Now, if some monitored issues in Jira got updated, Allure TestOps will receive a notification about these updates.
  • We’ve added support of a new feature called manual test cases as code which allows you keeping manual tests in the code alongside with your automated tests code.

πŸ”¬ Improvements

  • We’ve added some indexes that were missing. We’re trying to improve the performance of Allure TestOps.

🐞 Bug Fixes

  • We’ve fixed fidget buttons in modal windows. Some issues in the layout caused buttons were fidget. You’ll never see it again.

    ALT TEXT

12 Apr 2021 - Allure TestOps 3.170.1

πŸš€ New Features

Upcoming.

🐞 Bug Fixes

8 Apr 2021 - Allure TestOps 3.170.0

πŸš€ New Features

🐞 Bug Fixes

7 Apr 2021 - Allure TestOps 3.169.6

πŸ”¬ Improvements

Various dependencies updates. You won’t see it explicitly but it’s good!

🐞 Bug Fixes

1 Apr 2021 - Allure TestOps 3.169.5

🐞 Bug Fixes

28 Mar 2021 - Allure TestOps 3.169.4

🐞 Bug Fixes

24 Mar 2021 - Allure TestOps 3.169.2

🐞 Bug Fixes

19 Mar 2021 - Allure TestOps 3.169.1

πŸš€ New Features

Nope.

πŸ”¬ Improvements

🐞 Bug Fixes

18 Mar 2021 - Allure TestOps 3.169.0

πŸš€ New Features

Not today.

πŸ”¬ Improvements

🐞 Bug Fixes

09 Mar 2021 - Allure TestOps 3.168.0

πŸš€ New Features

πŸ”¬ Improvements

07 Mar 2021 - Allure TestOps 3.167.0

πŸš€ New Features

🐞 Bug Fixes

02 Mar 2021 - Allure TestOps 3.166.4

πŸš€ New Features

23 Feb 2021 - Allure TestOps 3.165.0

πŸš€ New Features

18 Feb 2021 - Allure TestOps 3.164.1

πŸ”¬ Improvements

11 Feb 2021 - Allure TestOps 3.163.0

πŸš€ New Features

πŸ”¬ Improvements

11 Feb 2021 - Allure TestOps 3.162.0

πŸš€ New Features

πŸ”¬ Improvements

🐞 Bug Fixes

26 Jan 2021 - Allure TestOps 3.161.2

🐞 Bug Fixes

21 Jan 2021 - Allure TestOps 3.161.0

πŸš€ New Features

πŸ”¬ Improvements

🐞 Bug Fixes

22 Dec 2020 - Allure TestOps 3.160.2

🐞 Bug Fixes

17 Dec 2020 - Allure TestOps 3.160.1

🐞 Bug Fixes

15 Dec 2020 - Allure TestOps 3.160.0

πŸš€ New Features

πŸ”¬ Improvements

🐞 Bug Fixes

08 Dec 2020 - Allure TestOps 3.159.0

We’ve changed the default settings of RabbitMQ and fixed some minor bugs.

πŸ”¬ Improvements

🐞 Bug Fixes

04 Dec 2020 - Allure TestOps 3.158.3

πŸ”¬ Improvements

01 Dec 2020 - Allure TestOps 3.158.2

🐞 Bug Fixes

01 Dec 2020 - Allure TestOps 3.158.1

🐞 Bug Fixes

23 Nov 2020 - Allure TestOps 3.158.0

πŸš€ New Features

20 Nov 2020 - Allure TestOps 3.157.1

πŸ”¬ Improvements

16 Nov 2020 - Allure TestOps 3.157.0

πŸš€ New Features

πŸ”¬ Improvements

🐞 Bug Fixes

11 Nov 2020 - Allure TestOps 3.156.1

πŸ”¬ Improvements

9 Nov 2020 - Allure TestOps 3.156.0

πŸš€ New Features

πŸ”¬ Improvements

🐞 Bug Fixes

27 Oct 2020 - Allure TestOps 3.155.1

πŸ”¬ Improvements

🐞 Bug Fixes

26 Oct 2020 - Allure TestOps 3.155.0

πŸš€ New Features

25 Oct 2020 - Allure TestOps 3.154.0

πŸ”¬ Improvements

18 Oct 2020 - Allure TestOps 3.153.1

🐞 Bug Fixes

15 Oct 2020 - Allure TestOps 3.153.0

πŸš€ New Features

πŸ”¬ Improvements

🐞 Bug Fixes

09 Oct 2020 - Allure TestOps 3.152.2

πŸ”¬ Improvements

08 Oct 2020 - Allure TestOps 3.152.1

🐞 Bug Fixes

07 Oct 2020 - Allure TestOps 3.152.0

πŸš€ New Features

πŸ”¬ Improvements

🐞 Bug Fixes

29 Sep 2020 - Allure TestOps 3.151.2

🐞 Bug Fixes

28 Sep 2020 - Allure TestOps 3.151.1

🐞 Bug Fixes

25 Sep 2020 - Allure TestOps 3.150.0

πŸš€ New Features

πŸ”¬ Improvements

16 Sep 2020 - Allure TestOps 3.149.0

Upgrade to 3.148.2 before install this update
Database update

  • New table for test case attachments
  • Move attachments to the new table

πŸ”¬ Improvements

🐞 Bug Fixes

16 Sep 2020 - Allure TestOps 3.148.2

πŸ”¬ Improvements

10 Sep 2020 - Allure TestOps 3.148.0

πŸš€ New Features

πŸ”¬ Improvements

03 Sep 2020 - Allure TestOps 3.147.1

🐞 Bug Fixes

03 Sep 2020 - Allure TestOps 3.147.0

πŸš€ New Features

🐞 Bug Fixes

01 Sep 2020 - Allure TestOps 3.146.0

πŸš€ New Features

🐞 Bug Fixes

26 Aug 2020 - Allure TestOps 3.145.1

🐞 Bug Fixes

24 Aug 2020 - Allure TestOps 3.145.0

πŸ”¬ Improvements

21 Aug 2020 - Allure TestOps 3.144.0

πŸš€ New Features

19 Aug 2020 - Allure TestOps 3.143.0

πŸš€ New Features

18 Aug 2020 - Allure TestOps 3.142.0

πŸš€ New Features

🐞 Bug Fixes

17 Aug 2020 - Allure TestOps 3.141.2

πŸ”¬ Improvements

13 Aug 2020 - Allure TestOps 3.141.1

🐞 Bug Fixes

07 Aug 2020 - Allure TestOps 3.141.0

πŸš€ New Features

🐞 Bug Fixes

04 Aug 2020 - Allure TestOps 3.140.0

πŸš€ New Features

🐞 Bug Fixes

03 Aug 2020 - Allure TestOps 3.139.0

πŸš€ New Features

03 Aug 2020 - Allure TestOps 3.138.1

πŸ”¬ Improvements

🐞 Bug Fixes

28 Jul 2020 - Allure TestOps 3.138.0

πŸš€ New Features

🐞 Bug Fixes

20 Jul 2020 - Allure TestOps 3.137.0

πŸš€ New Features

17 Jul 2020 - Allure TestOps 3.136.0

πŸš€ New Features

14 Jul 2020 - Allure TestOps 3.135.2

🐞 Bug Fixes

07 Jul 2020 - Allure TestOps 3.135.1

🐞 Bug Fixes

02 Jul 2020 - Allure TestOps 3.135.0

Database update
Add missing foreign key between test_result and test_layer tables.

πŸš€ New Features

πŸ”¬ Improvements

24 Jun 2020 - Allure TestOps 3.134.1

🐞 Bug Fixes

23 Jun 2020 - Allure TestOps 3.134.0

Breaking changes
Install new version of CI integrations firstly:

Database update
This update may take a very long time. Affect test_result table.
Migrate from execution to job run and session.

πŸš€ New Features

18 Jun 2020 - Allure TestOps 3.133.0

RabbitMQ update
Remove blob_task_remove queue.

πŸš€ New Features

πŸ”¬ Improvements