TestRail

xyva.ai integrates with TestRail to synchronise test cases and map execution results, keeping your test management system in sync with actual test runs.

API Credentials Setup

Navigate to Settings > Integrations > TestRail and configure:

Field	Description
TestRail URL	Base URL, e.g. https://yourorg.testrail.io
Email	Account email used for API authentication
API Key	Generated under My Settings > API Keys in TestRail
Project ID	Numeric TestRail project identifier

WARNING

TestRail API access must be enabled by an administrator under Administration > Site Settings > API. Without this, all API calls return 403.

Test Case Sync

xyva maps its internal test catalog to TestRail sections and cases:

xyva Catalog                    TestRail
─────────────────               ──────────────────
Suite: Login                →   Section: Login
  ├ valid-credentials.spec  →     Case C1001
  ├ invalid-password.spec   →     Case C1002
  └ lockout-after-5.spec    →     Case C1003

• Import pulls TestRail cases into the xyva catalog as read-only references.
• Export pushes new xyva test definitions to TestRail as draft cases.
• Sync performs a bidirectional merge, matching by case title and section path.

INFO

Sync uses the test file name as the primary matching key. Rename detection is not automatic -- if you rename a spec file, re-map it manually in the catalog.

Result Mapping

When a test run completes, xyva can post results to a TestRail run:

xyva Result	TestRail Status
Passed	Passed (1)
Failed	Failed (5)
Skipped	Blocked (2)
Timed Out	Retest (4)

Results include elapsed time, error messages, and a link back to the xyva run report.

Automatic Posting

Enable Auto-post results in the integration settings to push results after every Runner execution. xyva creates a new TestRail test run or appends to an existing open run based on the configured strategy:

• Per execution -- one TestRail run per xyva run
• Daily roll-up -- all results from the same calendar day in one run

TIP

Use the daily roll-up strategy for nightly regression suites to avoid cluttering TestRail with dozens of individual runs.

What To Read Next

• YouTrack -- issue tracking for failed tests
• Runner -- test execution engine