Publish test intent and evidence
Test Management Integrations
Keep native UI execution evidence connected to the team’s test-management system.
Explore source ↗Capability
One provider-neutral facade lets Test Studio and scripted flows publish cases, steps, runs, and evidence while each adapter preserves the external system’s planning model.
- 01
TestMo and TestRail
- 02
Xray and Zephyr Scale
- 03
Qase
- 04
Test Studio UI and Jint scripting facade
How it composes
From intent
to working system.
Configure
Test Studio stores provider endpoints, projects, suites, credentials, and mapping policy.
Map
A common model normalizes cases, folders, cycles, plans, runs, steps, and statuses.
Execute
Visual, YAML, CLI, or scripted flows produce the same structured result evidence.
Publish
Focused adapters translate evidence into each provider’s API without leaking provider details into flow logic.
Quick start
Adopt this
capability.
Start with the primary module, then add the related packages only when the application needs those layers. Replace VERSION with the current NuGet version.
dotnet add package Chrome.DevTools.Integration.Core --prerelease<PackageReference Include="Chrome.DevTools.Integration.Core" Version="VERSION" /><PackageVersion Include="Chrome.DevTools.Integration.Core" Version="VERSION" />const run = await Integrations.createRun("release-smoke");await Integrations.publishResult(run.id, { caseId: "login", status: "passed"});Modules in this capability
Use one layer.
Compose the rest.
Provider contracts, configuration, result models, and scripting facade.
↗02Chrome.DevTools.Integration.TestMoTestMo cases, runs, configuration, and step results.
↗03Chrome.DevTools.Integration.TestRailTestRail cases, plans, entries, separated steps, and results.
↗04Chrome.DevTools.Integration.XrayXray test import and manual step workflows.
↗05Chrome.DevTools.Integration.ZephyrZephyr Scale cycles, folders, cases, and execution results.
↗06Chrome.DevTools.Integration.QaseQase run mappings, cases, and step statuses.
↗Source of truth
Read the module beside the complete system.
The implementation, samples, issues, and release notes stay in the parent repository so module details remain connected to the product architecture.