30 October 2024 — Allure TestOps 5.11.5

15 October 2024 — Allure TestOps 5.11.5 (see here)

27 September 2024 — Allure TestOps 5.11.3

Starting from release 5.11.3, Allure TestOps will not start if the PostgreSQL database server version is below 15. This release requires an update to the configuration files.

Please refer to the configuration update page for details on the changes required before upgrading Allure TestOps to version 5.11.3.

Bug Fixes

• Fixed the issue where opening a saved filter with values for the Member parameter reset those values and resulted in a 400 error.
• Fixed the API request handling when an invalid token is used. Now it returns a 401 error instead of a 200 response.
• Fixed the issue where test results did not save user-specified details about the execution of steps with expected results.
• Fixed the incorrect display of test case statuses in the Jira plugin iFrame.
• Fixed the distribution of database connections between the main pool and the pool used for data migrations within the database.
• [5.11.4] Fixed the error “HTTP Status 500 — Internal Server Error” that occurred when attempting to authenticate users in Allure TestOps using Okta as the OpenID identity provider.
• [5.11.5] Optimized API query /api/evv/suggest to improve database performance under high load conditions.
• [5.11.5] Updated the versions of the plugins io.spring.dependency-management and org.springframework.boot used in Allure TestOps.see here

0 Votes