Visual native UI test authoring
Test Studio
Author serious native UI tests visually, declaratively, or both.
Explore source ↗Capability
A complete test-design workspace records interactions, synchronizes step lists with YAML, offers live selector IntelliSense and assertion inference, composes visual node flows, launches apps, runs suites, and presents screenshots, logs, telemetry, and reports.
- 01
Recording and visual node flows
- 02
Synchronized YAML with 50+ commands
- 03
Live selectors and assertion inference
- 04
Screenshots, telemetry, suites, and reports
How it composes
From intent
to working system.
Record
Pointer and focus events become stable selector-driven steps.
Author
Step list, YAML editor, IntelliSense, environments, and node graph stay synchronized.
Execute
Play, pause, stop, step, reusable flows, loops, scripts, and app launch drive the target.
Evidence
Assertions, screenshots, logs, CPU, memory, FPS, network, timing, and reports explain every result.
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 tool install --global Chrome.DevTools.Inspector --prereleasecdp-inspector# Connect Test Studio to the target CDP endpoint.cdp-inspector --url http://127.0.0.1:9222
# Record a flow, infer assertions, then run it# interactively or export the .flow.yaml file.Modules in this capability
Use one layer.
Compose the rest.
Desktop inspector and integrated Test Studio global tool.
↗02Chrome.DevTools.Inspector.SharedTest Studio models, flow execution, recorder, telemetry, and workspace composition.
↗03Chrome.DevTools.Inspector.ControlsReusable editor, chart, diff, overlay, and diagnostics controls.
↗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.