FAQ

Questions

Short answers for a local-first Chrome extension. If something still looks wrong, support is email — not a ticket portal.

• Is QA Studio Pro local-only? Do I need an account?

  Local-only. There is no account, no sign-in, and no cloud workspace. Install from the Chrome Web Store and start recording. Flows, variables, and run history never go to a QA Studio Pro server — there isn't one.

• Where does my data live?

  In this browser. Recordings, variable values, run results, and failure screenshots are stored in IndexedDB (and related browser storage) on your device. Run history keeps the newest 50 runs; older runs are pruned. Uninstalling the extension clears stored data.

  Data leaves the browser when you export a file, or when a step you add makes an HTTP request to a destination you choose. We do not receive those copies. Privacy policy.

• Why those Chrome permissions — and the debugger banner?

  Record and replay have to see the page you are exercising and fire real input. That means host access on the tabs you use, plus the debugger API (Chrome DevTools Protocol) so clicks and typing are real events, not a fake JS dispatch.

  Chrome shows a debugger banner while that API is attached. It is expected, not a malware warning.

  The Chrome Web Store lists categories such as personally identifiable information, financial and payment information, authentication information, web history, user activity, and website content because those can appear in a recording you make (a login form, a checkout, a URL). The extension stores that locally for replay. It does not send page content to us or to an AI service.

• How is this different from Playwright or Selenium?

  Playwright and Selenium are code-first automation frameworks. You write tests, run them in CI, pick browsers, wire reporters. QA Studio Pro is a Chrome extension that records a real-site flow and plays it back in this browser so you do not have to stand up a harness first.

  It is not a replacement for those tools. No grid, no multi-browser in v1, no CI worker inside the Chrome item. When a journey belongs in your pipeline, export Playwright TypeScript and own that file in your repo. Think of the extension as the capture and debug loop; think of Playwright/Selenium as the engineered suite.

• Does v1 include AI?

  No. No AI healing, no model that reads your page, no “self-fixing” selectors. Page content is not sent to any AI service. If AI shows up later, that will be a later release — not this local v1.

• Is there a cloud, team plan, or paid tier?

  Not in v1. The extension is free on the Chrome Web Store. Paid plans, seats, shared projects, and cloud sync are post-v1 and are not part of this release. Do not expect a billing page or an org switcher in the extension today.

• Do you collect telemetry or analytics?

  No. No product analytics, no crash reporter that phones home, no usage pings. If a network request happens during a run, it is because your flow navigated or you added an API step to a host you named.

• Which browsers are supported?

  Chrome, via the Chrome Web Store listing (Manifest V3). Replay depends on Chrome's debugger API. There is no Safari/Firefox/Edge store listing in v1, and no promise that unpacked loads elsewhere will behave the same.

• Is it free?

  Yes. Add it from the Chrome Web Store. No trial clock and no account gate.

• What does not work well?

  Closed shadow DOM is session-scoped and can still fail on some hosts. Virtualized lists need a recorded scroll. File-upload replay needs an absolute path set after record. Complex rich-text editors may need a script step. The debugger cannot attach to chrome:// or the Chrome Web Store. Record and replay guides list the same limits.

Still stuck? Email thisisganesh353@gmail.com.