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

TestRail Released

TestRail has been released today with an enhancement that ensures our Jira Add-On users will be able to continue working in both TestRail and Jira without disruption once Chromium SameSite updates are enforced (expected next week).

As detailed below, TestRail Cloud users have been automatically updated to the latest & greatest version.

We recommend that TestRail Server customers update to the latest version only if needed for the Jira add-on.

Update February 14, 2020: This TestRail version may affect users with older Chromium browsers. If you use the latest TestRail version, we recommend updating your browser(s) as well.

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:

TestRail Enterprise

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


With regards to the changes required for the SameSite updates - the problem created by this change in Chrome (and other browsers soon) is that Jira will always display the “You are not yet logged in to TestRail” message.

I’ve been looking at the impact, and available workarounds this morning, and have come up with the following for those who are hosting TestRail on IIS and are unable to upgrade TestRail immediately.

This involves updating the web.config file to add URL rewrite rules, which append the required cookie parameters to the outbound responses. This was based on information from

		<rule name="Add SameSite None" preCondition="No SameSite">
			<match serverVariable="RESPONSE_Set_Cookie" pattern=".*" />
			<action type="Rewrite" value="{R:0}; SameSite=None" />
		<rule name="Add Secure" preCondition="No Secure">
			<match serverVariable="RESPONSE_Set_Cookie" pattern=".*"/>
			<action type="Rewrite" value="{R:0}; Secure" />
			<preCondition name="No SameSite">
				<add input="{RESPONSE_Set_Cookie}" pattern="." />
				<add input="{RESPONSE_Set_Cookie}" pattern="; SameSite=None" negate="true" />
			<preCondition name="No Secure">
				<add input="{RESPONSE_Set_Cookie}" pattern="." />
				<add input="{RESPONSE_Set_Cookie}" pattern="; Secure" negate="true" />
1 Like