Visual native UI test authoring

Test Studio

Author serious native UI tests visually, declaratively, or both.

Explore source
Parent systemCDP
StatusPreview
Modules3
RepositoryCDP/CdpInspectorApp

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.

  1. 01

    Recording and visual node flows

  2. 02

    Synchronized YAML with 50+ commands

  3. 03

    Live selectors and assertion inference

  4. 04

    Screenshots, telemetry, suites, and reports

From intent
to working system.

01

Record

Pointer and focus events become stable selector-driven steps.

02

Author

Step list, YAML editor, IntelliSense, environments, and node graph stay synchronized.

03

Execute

Play, pause, stop, step, reusable flows, loops, scripts, and app launch drive the target.

04

Evidence

Assertions, screenshots, logs, CPU, memory, FPS, network, timing, and reports explain every result.

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.

01 · Install
Terminal
dotnet tool install --global Chrome.DevTools.Inspector --prerelease
cdp-inspector
02 · Use · bash
Terminal
# 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.

Use one layer.
Compose the rest.

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.

CDP

Search everything.

Loading the index…

move open esc close

Preparing metadata and full-text search…