Skip to main content

​
Overview

This integration enables your automated test suite to:
  • Automatically create test runs in a designated TestRail project.
  • Sync test results (e.g., passed, failed, skipped) to TestRail after your tests complete.
  • Complete test runs after tests are completed
Note: The integration currently supports syncing results to a single TestRail project.

​
How It Works

1
Trigger your automated test suite.
2
The integration identifies the relevant test cases and creates a new test run in your configured TestRail project.
3
Test results are reported back to TestRail in real-time or after the suite finishes.
4
Each test case’s status (e.g., passed, failed, skipped) is updated accordingly in the test run.

​
What Gets Synced

  • Test results: passed, failed, and skipped
  • Test run metadata: name, run/bug link

​
Requirements

Before getting started, make sure the following are set up on your end:

​
TestRail Configuration

  • ✅ Active TestRail account
  • ✅ API access enabled: Must be configured by a user with Administrator privileges
  • ✅ Project: A dedicated project in TestRail where results will be posted
  • ✅ Custom test status skipped :Must be added to your TestRail instance via the Admin panel

​
Authentication

Provide the following to QA Wolf:
  • Username or email associated with your TestRail account
  • API key or password (depending on how your account is configured)

​
Setup Instructions (Step-by-Step)

1

Verify API Access

  • Log into TestRail as an Administrator.
  • Go to Administration > Site Settings > API and ensure “Enable API” is checked.
2

Create or choose a TestRail project

  • This project will serve as the destination for all synced test runs.
  • Share the project ID or URL with your integration provider.
3

Add the skipped status

  • Go to Administration > Customizations > Result Fields.
  • Under the “Status” field, add a new status called skipped.
4

Share credentials securely

  • Provide your TestRail login or API key to QA Wolf.
  • Never include credentials in plain-text emails or public documents.
5

Verify with a test run

  • Once set up, trigger your test suite and confirm that a run appears in TestRail.

​
Frequently Asked Questions (FAQ)

If your suite references a test case ID that doesn’t exist, it will be skipped or cause an error — depending on your configuration. We recommend ensuring all referenced test cases are already created in TestRail.
Not currently. The integration supports syncing to one TestRail project at a time. Multi-project support is under consideration for future updates.
Yes, depending on your configuration, we can support mapping based on test titles, case IDs, or custom tags.

​
Support

Need help setting up the integration? Reach out to our support team or your dedicated customer success manager. We’ll walk you through the setup and validate everything is working as expected.

​
Known Limitations

  • ✅ Supported TestRail environments: Cloud-hosted (latest)
  • ⚠️ Limitations:
    • Only one project supported
    • Requires custom status configuration (skipped)
    • No support for test plan-level updates at this time
Last modified on February 9, 2026