Subscribe Join 180,000+ subscribers and receive articles from our blog about software quality, testing, QA and security. Subscribe

TestRail 6.5.5 Released

TestRail 6.5.5.1009 has been released with DB query performance improvements

  • Various database queries on which the TestRail views, summaries, dashboards, reports etc. rely have been improved to make them more performant.
  • A couple of the query changes caused problems for some customers, on the Milestone Progress and Test Case Defects views. Those issues have now been fixed also.

Getting TestRail 6.5.5

A 14-day trial version of TestRail can be requested here (hosted on our servers or as download to install on your own server): http://www.gurock.com/testrail/trial/

If you want to create a subscription for TestRail Cloud, you can do so from within TestRail via Administration > Subscription . Or, if you want to order TestRail Server licenses you can do so from our website here: https://secure.gurock.com/customers/shop/annual/purchase/

Registered customers can download the full version from our customer portal: http://www.gurock.com/portal/

Updating to TestRail 6.5.5

TestRail Cloud instances are automatically updated to the latest version. You can check your version via the TestRail Help > About TestRail menu item.

If you are using the on-premise version of TestRail, you can update to the new version as usual by installing it over your existing TestRail installation (there’s no need to uninstall your existing installation). Please see the update instructions for details: http://docs.gurock.com/testrail-admin/installation-upgrading/

If you’re using Docker, please refer to the instructions here: http://docs.gurock.com/testrail-admin/installation-docker

TestRail Enterprise

If you’re interested in our Enterprise package, please email us for a trial or quote via contact@gurock.com, or you can use the contact form here: https://secure.gurock.com/customers/support/

1 Like

See my comment on the 6.5.3 post. Does this version fix the following error occurring when attempting to Push a Defect to Jira?

Error: “Form field “component” does not specify a field type.”

Anyone on this thing?

Hi @steven.ogran,

Thanks for the follow-up. The error you are receiving is due to a slight change in the integration for Jira. To resolve the issue, simply change the ‘component’ field to ‘components’ (adding the ‘s’). You can find additional details and related screenshot here.

Hope this helps,
Jon