Frequently asked questions

From one recording: a runnable Playwright test in TypeScript, numbered Manual Steps in plain English and a Gherkin scenario, generated live and always in sync, plus a .webm video of the session. See Generated output and Session video.

Actify Studio is free, updates included. Install it from the Microsoft Store on Windows 10 or Windows 11 (64-bit). See Install and first launch.

No. You record by using your site, and refine steps on cards. Manual Steps and Gherkin are plain English anyone can read. The Playwright code is there for those who want it, but you never have to touch it. See Getting started.

Only to run tests. Recording, code generation and page inspection work without it. If it is missing, the Runner tells you and offers Download Node.js. See Requirements.

No. Actify Studio is a Windows app, for Windows 10 or Windows 11 (64-bit). See Requirements.

Chromium. You record in the real Chromium browser built into the app. Tests run either Headless, in a separate invisible browser installed once with the test runner, or In-App, visibly in a tab of the app’s browser. See Run options.

Yes. Attach a test data table (typed in or imported from CSV): the test runs once per row and each row gets its own result. For values that should simply change at every run — a new email, a random name, a date — use dynamic data.

Mark the step as Optional: if the element does not appear within a few seconds, the step is skipped and the test continues. See Optional steps.

The test repeats the email you typed while recording, and the site accepts it only once. On the step card, replace the value with a random one from the { } menu, e.g. {{email}}, or randomize only part of it (mario+{{random:6}}@test.it). To log in later with the same email, save it as a variable. See Dynamic data and variables.

Usually not. Each step stores several alternative locators: on the step card, pick another one from the locator dropdown (the colored dot shows how robust they are). If many tests use the same page, a Page Object lets you fix an element in one place. See Step card.

Yes. Load it with Load into recorder from the Workspace, edit the steps on their cards, add new ones at the end with Record or in the middle with + → Record from here, then Save again. See Editing an existing test.

The Runner output marks the failed step with ✗, the reason and the line of the test file. The Screenshots tab shows the page where the test stopped, with the element highlighted; turn on Steps to get a screenshot of every action. Report opens the full HTML report. See Results and Step screenshots.

Yes. Links that open a new tab open as tabs inside the app and the test follows them. Alert, confirm and prompt dialogs are recorded with your answer and replayed. Uploaded files are copied into the project so the test works on any PC. See Pages that open new tabs and Dialogs and uploads.

Yes. The generated code is standard Playwright: add a test to your existing suite, or export the whole project as a standalone Playwright project that runs anywhere Node.js is installed, CI included. Nothing proprietary to adopt. See Export.

On your PC, in C:\Users\<you>\Actify-Studio: projects, tests, Page Objects, flows, reports and videos. No account, no sign-in, no telemetry: the app does not send your tests or recordings anywhere. See Privacy and data.

Store them as secrets: they are encrypted on your PC, per environment, and the test only contains a reference such as {{secret:password}}. When you record a password field, the step card offers Save as secret to do it in one click.