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

Announcing TestRail 6.5: New Plugins, Enhanced Integrations & Searchable Drop-downs

We’re excited to announce the general availability of TestRail 6.5 for both our Professional and Enterprise Cloud and Server customers.

The main focus of this release is improved defect and reference plugin integrations, allowing teams to customize the defect and reference plugins available in TestRail. Not only did we update plugins for 15 existing integrations, but we’ve also added integrations with 5 new tools: Asana, Azure DevOps, GitLab, Trello, and VersionOne.

In addition to expanding the functionality of new and existing defect plugins, many dropdown menus throughout TestRail’s UI are now searchable. This can be a time-saver in areas where long lists of options are possible (like the assignee field).

Keep reading for more details on these changes.

Updated Defect and Reference Plugins

Prior to this release, the Jira plugins were the only ones that provided configurable push dialogs. In our 6.5 release, both Defect and Reference plugins now allow you to customize the fields which appear when using the plugin. Defect plugins provide a dialog for creating a new issue in your external tool (available in the ‘Defects’ menu, or while adding Test Results) and also allow you to hover over IDs in the Defects field of test results. Reference plugins allow you to retrieve data from your external tool while hovering over IDs in the References field of various TestRail entities (runs, cases, milestones, etc.).

Here is a full list of plugin functionality TestRail now supports:

Updating Your Plugin

With this new release, teams who are interested in using the new functionality may need to reset their plugin configuration. The steps are simple, but must be performed by an administrator:

  1. Navigate to the administration area for global integrations (or project settings for project-level integrations)
  2. Copy your existing connection settings into a temporary text file, sticky note, etc.
  3. On both the Defects and References tabs, change the plugin to the blank value at the top of the list
  4. Save your settings
  5. Go back to the Defects and References tabs and choose your tool
  6. Copy your connection settings values back into the plugin settings.
  7. Save your integration settings.

This will set your plugin with a default configuration, allowing you to make further changes if desired.

Configuring Defect and Reference Plugins

To customize the plugins, administrators can edit the [push.fields] and/or [hover.fields] sections of a plugin configuration and also add custom fields with most tools.

If you use the same tool for defects and references, you can copy and paste the connection settings and [hover.fields] section between the two plugin configurations, eliminating the need to manually customize both.

Let’s look at the default Trello configuration, which will allow teams to create new Trello cards from within TestRail and look up card details by hovering over card IDs. TestRail will support some default fields out of the box, allowing you to quickly turn them ‘on’ or ‘off’:

Please keep in mind that some tools have fields that are always required (such as a title or name), so these fields will always be enabled by the plugin. We’d recommend testing the new plugins with the default configurations first, then adding customizations as needed. You can find full documentation for all plugins in our user guide here.

Searchable Dropdown Menus

Throughout TestRail, we’ve updated many dropdown menus to provide search capabilities. This should speed up your testing efforts by helping your testers find assignees and other values quickly.

TestRail for Jira Add-on Changes (Jira Cloud only)

Some users reported issues configuring the TestRail for Jira Add-on in Jira Cloud instances. The add-on would not save changes to project selection in some instances. This issue has been addressed and Jira Cloud customers should automatically receive the add-on update.

Getting TestRail 6.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

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/

As with all updates, please ensure you make a backup of your current on-premise installation before upgrading to the new version.

If you’re using Docker, please refer to the upgrade and installation 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/

Hi @sjpknight

Thanks for this, does this version fix the issue with Docker that existed in the previous version do you know?

Is there a changelog anywhere that could help identify exactly what’s in the versions?

Thanks again

severe issues with new version (6.5.0.1298 cloud version)
among them:

Is there a list with plan for fixing them? Is it possible to revert cloud version to last stable one?

Hi @Tomasz,

We have been made aware of an issue which may affect some teams with certain field configurations.

We believe we’ve been able to identify the cause of the issue and are working on a fix to be released as soon as possible.

In the meantime, can you let me know if the following workaround allows you to continue using TestRail normally:

Navigate to 'Administration > Customizations'
Edit the 'Automation_Type' field
Apply this field to all test case templates

I understand teams may not want this field to appear in every test case. However, this may be a workaround to the current issue in the meantime.

Thanks,
Jon

It was already set that way. I need to deactive this field to be able to save edited TC

Hi @Tomasz

Thanks for the feedback and workaround! We are working on a fix for this issue to be released as soon as possible so teams can continue to use (or not use) the automation_type field as they wish.

Regards,
Jon

Hi,

I just wanted to report that we’re also having the problem that Tomasz is describing. It’s completely blocking 3 project teams from creating or editing any test cases. Same thing, the main issue is with the steps field and a dropdown field that we have. The UI is unresponsive and shows javascript errors.

Cheers,
Chris

Hi,

I caught a problem while updating the database (when updating from the TestRail version 6.3.0.1120 -> 6.5.0.1298) - “Duplicate column name ‘refs’”
How do you recommend fixing the problem?

Hi @nekrasovam,

So we can look into this issue further and if you haven’t already done so, can you reach out to our support team at contact@gurock.com? We should be able to walk through a resolution to this error so you can complete the upgrade.

Regards,
Jon

Hi @ChowellGram,

Can you let me know if the steps described in my previous response resolve the issue for you?

Regards,
Jon

Hey Jon,

Ah - yes it has. Thanks for the workaround

Cheers,
Chris

I caught a problem while updating the database (when updating from the TestRail version 6.3.0.1120 -> 6.5.0.1298) - “Duplicate column name ‘refs’”
How do you recommend fixing the problem?

Support advised to execute a query in the database
mysql> alter table milestones drop column refs;
This solution worked for me!

2 Likes

In a dark theme, the input field has a dark font!
It’s very gothic! :smiley:


@nekrasovam

Hey Artyom,

This has been notified earlier and we have logged an issue for the same. Thanks for pointing it out though. :slight_smile:

Regards,
Shanu

1 Like

Are the docker images available for 6.5? I don’t see any recent updates for these, they all seems to be a month old? https://hub.docker.com/u/testrail

6.5 has created a problem when editing test cases where the Milestone drop-down is too long and covers the References drop-down. Is there a workaround?

TR_Milestone_References_Overlap

Hi,

is it possible to receive JSON response from this error?
image
I’m trying to configure new Azure DevOps plugin but I have received this error (“Push” option") and currently I have no idea what to do next. Unsername, password etc are correct, otherwise I had 401 error.
Is there any documentation how to properly configure this plugin?

Regards,
Danny

Can we disable the searchable dropdowns in the Results dialog? Before this feature was added, I could quickly tab through each field, type the first letter of the drop-down item for quick entry. Now, tabbing is cumbersome at best and I must click into the field with a dropdown to begin typing/searching for the entry I want. Definitely not speeding things up. :roll_eyes:

1 Like

Its amazing that Gurock havent responded to this basic issue. There have been so many problems reported in the current release.
Please note this is for the references field being overwritten by previous field.
A work around for this which we identified was to increase the size of the window by clicking on the edge at the right hand size of the frame and re-sizing. Another method is to zoom in by Ctrl and -.
An extreme work around is by maintaining your tests in excel and loading it into TestRail finally.

Hi,
I want to ask is it possible to clean dropdown fields selection. Field is not required with default empty state. Before 6.5 release it was possible to choose empty field state from any selection. Now it isn’t. I don’t want to add new empty value here and bulk change all TC.
Is it possible to restore previous behaviour?
Regards,
Tomasz