Skip to content
Now on the Microsoft Store

Stop writing tests.
Start recording them.

Actify Studio watches you browse and builds a full test framework: Playwright specs, human steps, Gherkin, Page Objects, reusable steps, and a session video, from one recording. No code, no setup.

localhost:3000/#/
REC
One recording  →  everything you need to ship
Playwright TSHuman StepsGherkin BDDPage ObjectsReusable stepsNo-code frameworkAI agents (MCP).webm video8 locators13 assertsZero boilerplateNo setupEditable history50× undo
The foundation

Seven things captured.
One recording.

Every Actify Studio session captures seven dimensions of the user journey, each one becomes test code, locators, and a video, without you writing a line.

Clicks

every tap

Buttons, links, tabs, checkboxes, de-duplicated.

Fills

all inputs

Text, selects, keystrokes. Flushed on blur.

Navigates

tracked

URL bar, links, programmatic, survives transitions.

Locators

8 strategies

testId, role, label, text, id, CSS, XPath, ranked.

Asserts

13 types

Visibility, text, state, count. Negate + soft.

Video

25 Mbps

.webm of the browser view, bundled in.

Outputs

3 formats

Playwright TS, steps, Gherkin, synced.

+ a video, every time

No external screen recorder. The session ships with the spec.

Triple output

One recording.
Three production-ready outputs.

Playwright TypeScript, human-readable steps, and Gherkin BDD generate at the same time, always in sync. No copy-paste, no drift.

test.spec.tssteps.mdflow.feature
import { test, expect } from '@playwright/test'; test('Recorded QA flow', async ({ page }) => { await page.goto("http://localhost:3000/#/"); await page.getByTestId("login-link").click(); await page.getByTestId("login-email").click(); await page.getByTestId("login-email").fill("demo@acme.test"); await page.getByTestId("login-password").click(); await page.getByTestId("login-password").fill("demo1234"); await page.getByTestId("login-submit").click(); await expect(page.getByTestId("user-avatar")).toBeVisible();});
# Test Steps 1. Navigate to http://localhost:3000/#/2. Click on "Log in"3. Click on "Email address"4. Type "demo@acme.test" into "Email address"5. Click on "Password"6. Type "demo1234" into "Password"7. Click on "Sign in"8. Assert that "JD" is visible
Feature: Recorded QA flow Scenario: User flow execution Given the user navigates to http://localhost:3000/#/ When the user clicks on "Log in" And the user clicks on "Email address" And the user types "demo@acme.test" into "Email address" And the user clicks on "Password" And the user types "demo1234" into "Password" And the user clicks on "Sign in" Then the user should see "JD"
The case

Built for the way you actually test.

Record once, edit like a human, ship in your stack. Every captured action is yours to reorder, rename, or turn into an assertion.

Download free

Triple output, always in sync

Playwright TS, human steps, and Gherkin generate together from one session.

Session video, bundled

A .webm of your exact run ships with every test. No screen recorder.

Point. Pick. Assert.

Click a condition, click an element, the assertion writes itself.

Editable history

Reorder, duplicate, delete, re-pick locators. Undo/redo 50 deep.

Run it without leaving

Replay any test in-app or headless, pass/fail, slow-mo, grouped into suites.

Reuse, the real way

Turn recordings into Page Objects and reusable steps, like a login shared by every test. No throwaway scripts.

No code required

Not a coder?
No problem.

Click through your app like a user. Actify Studio turns every action into production-ready Playwright, you never write a selector, and your team never inherits throwaway code.

01

Record by clicking

Browse your app exactly as a user would. Every click, fill, and navigation is captured live, no scripting.

02

Real code, generated

Out comes genuine Playwright TypeScript, human steps, and Gherkin, ranked locators, real assertions. Not pseudo-code.

03

Hand it to your devs

Standard files drop straight into your existing suite, config, and CI. Nothing proprietary to adopt or maintain.

No-code framework

A real automation framework.
Without writing a line.

Most recorders stop at a throwaway script. Actify Studio assembles a maintainable Playwright framework, Page Objects, reusable steps, suites and environments, all built by clicking, never by coding.

Page Objects

Every element a test uses lands in a Page, named and linked. Fix a locator once and the app offers to update every test that uses it.

Reusable steps

Record a login once, give it inputs, and drop it into any test. Change it in one place and every test that uses it follows.

Run it anywhere

Replay tests in the embedded browser or headless on Chromium, Firefox and WebKit. Suites, tags, retries, run history and traces built in.

Environments

One project, many baseURLs. Record on dev, run the same suite on staging or prod by switching a dropdown, paths stay relative.

Export & own it

Eject a standalone Playwright repo with a ready CI pipeline: npm i && npx playwright test. Standard files, nothing proprietary to keep.

One Project tab

Tests in folders, tags, suites, Pages and API collections in one place. Ctrl+P opens anything, never a terminal.

Start building

From first click to a maintainable suite, you never touch a config file.

AI agents · MCP

Your AI assistant,
now on your QA team.

Connect an MCP-compatible AI app, such as Claude Code or Claude Desktop, to Actify Studio. It records and edits tests in the app’s browser, runs them, works out why they fail and writes the bug report, while you watch every step.

  • Records tests you can readEvery action the agent takes becomes a step card, with checks and variables, saved as a normal test you can open and edit.
  • Runs, triages, reportsIt launches a test, a tag or a suite, reads the failed step and its screenshot, then files a bug report with steps, network calls and console errors.
  • Thinks like a testerIt follows a QA playbook and your project’s guidelines: negative and edge cases, solid locators, and never weakening a check just to turn a test green.
AI agent connectedMCP clientDisconnect

Record a checkout test with an expired coupon, then run the smoke tag.

  1. get_qa_guideproject guidelines + QA playbook
  2. start_recording/login
  3. fill"Email" ← {{email}}
  4. fill"Coupon" ← "SPRING-EXPIRED"
  5. add_assertion"Coupon expired" is visible
  6. save_testcheckout_expired_coupon @smoke
  7. runtag @smoke · Chromium, Firefox, WebKit
  8. wait_run1 of 6 failed · WebKit
  9. report_bugBUG-007 · Major · total ignores the discount

Saved 1 test with 2 checks. The WebKit failure looks like an app bug, so I filed BUG-007 and left the check as it is.

Stays on your PC

The AI app talks to Actify Studio through a local connection on your computer. Actify Studio has no AI of its own and sends nothing anywhere.

You set the permissions

Read only, Test, Edit or Full. Deleting or replacing a test always waits for your OK in the app.

Every action on record

A bar shows what the agent is doing, with Disconnect one click away, and the Activity log keeps track of every change it makes.

Works with any MCP-compatible AI app, for example Claude Code or Claude Desktop. Off until you turn it on.

Connect an AI agent
Free on Windows

Record your first test today.

Install Actify Studio from the Microsoft Store, open any site and start recording. Your Playwright test writes itself.

Download from the Microsoft Store
Windows 10 / 11 (64-bit)FreeUpdates via the Store

New here? Follow the installation guide.

Actify Studio — Stop writing tests. Start recording them.