Skip to main content

Connect TestRail to Hive

See TestRail runs and test cases directly in Hive chat. Connect your workspace’s TestRail Cloud account to turn shared links into cards with details from TestRail.

Written by Ellen Kajca

Before you start

You’ll need:

  • Workspace admin access in Hive.

  • A TestRail Cloud address, such as https://yourcompany.testrail.io.

  • A TestRail account email and API key.

We recommend using a read-only TestRail account with access to the projects your team needs.

Who can see card details? Cards use the connected account’s permissions. Internal workspace members can see details that account can access, even without their own TestRail account. External workspace members see plain links.

Self-hosted TestRail and on-premises aren’t supported.

Connect your account

  1. Open Apps in Hive.

  2. Find TestRail and select Open.

  3. Enter your TestRail address, Account email, and API key.

  4. Select Connect.

Hive checks your connection. When setup succeeds, you’ll see Connected, and TestRail cards will be enabled.

Your API key is stored encrypted. When editing the connection later, leave the API key field blank to keep the saved key.

Share TestRail links in chat

Paste a TestRail run or test case link into Hive chat. Links from your connected TestRail instance display as cards.

Links from other TestRail instances remain plain links.

Test or update your connection

Open Apps → TestRail → Open.

  • Select Test connection to check your saved connection.

  • Update your address, account email, or API key, then select Save changes.

If you see Needs attention, review the error shown in the dialog. Check your TestRail address, credentials, and the connected account’s project access, then save your changes.

Turn cards off or disconnect

To stop displaying cards while keeping your connection settings, turn off TestRail using its toggle on the Apps page.

To remove the connection, open TestRail and select Disconnect. TestRail links in chat will display as plain links again.

Did this answer your question?