Actify Studio documentation
Turn manual browser testing into automated tests, without writing code.
What Actify Studio is
Actify Studio turns manual browser testing into automated tests without writing code. It is a desktop studio with a real Chromium browser built in. You open your web application inside the app and use it normally; every click, typed value, dropdown choice and key press is recorded as a step.
The steps are translated live into three formats: a runnable Playwright test, numbered Manual Steps in plain English, and a Gherkin (BDD) scenario. Saved tests run from the app itself on Chromium, Firefox and WebKit, and a whole project can be exported as a standalone Playwright project with a ready CI pipeline.
Actify Studio is a free Windows desktop app, available through the Microsoft Store. These guides describe version 1.2.0: AI agents, API testing and mocks, phones and tablets, several browsers, run history and traces, Reusable steps, bug reports and much more — see What’s new in 1.2.0.
New here? Start with Getting started: install the app, then record, save and run your first test in five minutes. To let an AI app such as Claude work with you, see AI agents.
Guides
Get started
Recording
Dynamic & data-driven tests
API & network
Organize & reuse
Running
AI agents
Reference
Key concepts
The words used across these guides, in plain language.
| Term | Meaning |
|---|---|
| Step (action) | One thing the user did or checked: navigate, click, type, select, press a key, hover, drag, upload a file, answer a dialog, wait, a check, an API request or a mock. |
| Locator | How the test finds an element on the page again (by test id, role and name, label, placeholder, text, CSS or XPath). Each step stores several alternatives. |
| Check (assertion) | A step that makes the test pass or fail, e.g. “this button is visible” or “this text equals Welcome”. |
| Page | A reusable description of one screen of your site: its named elements. Steps that use those elements are linked to them, so a changed element is fixed in one place. |
| Reusable steps | A group of steps recorded once — a login, adding a product to the cart — and used in many tests, with Inputs for the values that change. |
| Suite | A named group of tests you run together. |
| Tag | A label such as @smoke on a test, to find and run every test that has it. |
| Project | A self-contained folder with its own tests, Pages, Reusable steps, API collections and settings. |
| Environment | A named server for a project (e.g. dev → http://localhost:3000), with its own variables and secrets. Switching environment runs the same tests against another server. |
| Headless / In-App | The two run modes: in hidden background browsers, or visibly inside the app’s browser. |
| Dynamic value | A value generated at each run instead of a fixed one, written as {{…}} — e.g. {{email}} for a random email. |
| Variable | A value saved by one step (a typed value, the text of an element, a value of an API response) and reused by later steps as {{name}}. |
| Test data | A table attached to a test: the test runs once per row, and each row gets its own result. |
| Secret | A password or token stored encrypted on your PC, per environment, and used as {{secret:name}} — never written into the test. |
| AI agent | An MCP-compatible AI app on your PC (for example Claude Code or Claude Desktop) that you allow to read, record and run tests in Actify Studio. |
Something unclear or missing? Write to info@actify-studio.com.