QA Studio Pro
Add to Chrome

Docs

Export

Export a flow as JSON, YAML, or a Playwright TypeScript file. That is the moment a copy leaves the browser — because you asked, not because we sync.

Formats

  • JSON — a structured copy of the flow for backup or moving to another machine yourself
  • YAML — same idea, easier to skim and diff in a text editor
  • Playwright TypeScript — a starting point you drop into your own Playwright repo

JSON and YAML

Use these when you want a file you control. Copy it to another Chrome profile, keep a backup, or review steps in git. QA Studio Pro does not host the file. If it contains variable values, treat it like any other secret-bearing artifact.

Playwright TypeScript

When a journey has earned a place in CI, export TS and take it into the project that already runs Playwright. From that point the test is yours: browsers, fixtures, reporters, grid. The extension is not a CI runner and does not talk to your pipeline.

Export is a handoff, not a sync. Edit the generated file like any other test. See vs Playwright and Selenium.

Optional local CLI

A local CLI runner exists for power users. It is not part of the Chrome Web Store item. If you are only using the extension, you can ignore it.

What export is not

Not cloud sync. Not a team workspace. Not telemetry. The other way data can leave the browser is an HTTP step you add, to a destination you type. Those requests are yours. We do not receive them.