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

TestRail 6.4.0.1293 Released

TestRail 6.4.0.1293 has been released today with fixes for the following issues:

  • Push defect from anywhere functionality re-enabled (we discovered that ALL attachments were being sent to the integrated tool, and disabled it for a period to prevent this from happening).
  • When using a defect plugin and then hovering over Defect IDs in TestRail, IDs which included a hyphen (such as Jira IDs) were not being retrieved.
  • When hovering a reference plugin and then hovering over a Reference ID, users were seeing a “User does not have a valid OAuth connection” error after the 6.4 release, as reported here.
  • In some situations where the Separated Steps field was deleted by an administrator, and recreated at a later time, Fast Track editing could cause the deletion of a test case’s separated steps.

Using Assembla?

If you have TestRail integrated with Assembla, please update your Defect and Reference View URLs to: https://app.assembla.com/spaces/yourspacenamehere/tickets/realtime_list?ticket=%id%

If your Assembla instance is located in the EU, please use https://eu-app.assembla.com/spaces/yourspacenamehere/tickets/realtime_list?ticket=%id% (instead of https://app.assembla.com…)

Complete integration documentation can be found here.

Getting the new version

Updating to the new version

  • 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). The database upgrade wizard is automatically started when you access TestRail with your web browser. Please see the update instructions for details: http://docs.gurock.com/testrail-admin/installation-upgrading/

TestRail Enterprise

Please ensure you make a backup of your current on-premise installation before upgrading to the new version.

@sjpknight after the 6.4 release my automation test scripts are not pushing the results to Testrail. I am getting this error. - " TestRail API returned HTTP 403 ({‘error’: 'Access Denied. You are not a TestRail administrator. Field:project_id is a required field. When i check the API manual doc it says the due to insufficient permission we can get this error. But there was no changes being done from Administrator. Can anyone please help . I am stuck with this error from last 3 days

Hi @saikat.debnath - can you send some more details about the specific request(s) being made to our support team via contact@gurock.com please?

Once we’ve got those, we’ll be happy to look into the situation further for you.

Cheers,
Simon

@sjpknight sent details to the mail you mentioned, waiting for the response. Thanks for your reply

I just tried to update from version 6.2.x to this version with docker and I failed on db update 213. I think my initial update was 202.

Not sure if anyone else had the problem "Duplicate column name refs"

This is within Docker, to update this post, support said there is an issue with the docker containers. So hoping this fix when complete fixes my problem

We have tried to upgrade TestRail to version 6.4 today and we are receiving an error - as I am new to this forum I cannot post a copy of the error but its basically

Duplicate column name ‘refs’

Desperately need some help with this please. I have tried support but have heard nothing back.

Yes, that’s the exact same error that I am getting

My message directly above yours says that this is an issue with their docker images. I had some good dialogue yesterday, we should watch this thread or the testrail news for new updates to the docker versions. Unless you manually want to drop the column refs from the milestone table and rerun the db upgrade

Any idea on a timeline for the docker container fix?

Hey,

I can see Jon’s response to this question on the other post.

Hope, this helps !

Thanks,
Shanu