Skip to content
WeftKit

Recording studio

The studio is where a workflow becomes a test. You launch a browser from WeftKit, perform the journey once the way a person would, and the app records the intent behind each interaction — not a coordinate trace, and not your screen.

The WeftKit Recording Studio with an empty active-capture state, a Start a recording button, and a list of recent captures showing step, click, screenshot, and duration counts.
The studio between captures. Recent captures carry their step, click, screenshot, and duration counts.

An isolated browser, not yours

WeftKit launches its own browser profile and records only that window. It does not attach to your personal browser, and it does not observe input outside the session it started. Your cookies, extensions, saved passwords, and open tabs are not part of the capture.

Technical capture starts before the first navigation, but the semantic timeline begins only when you interact with the launched browser — so the setup navigation never becomes step 1.

What a step records

Each interaction is compiled into a semantic action with the context needed to replay it somewhere the DOM has shifted slightly:

What WeftKit stores for each recorded step
RecordedWhy it exists
The actionOne of navigate, click, fill, select, press, tab, or assert — the intent, expressed independently of implementation code.
A locator fallback ladderSeveral ways to find the same element, ordered by durability, so a class-name change alone does not break the step.
Bounded evidenceViewport screenshots at action boundaries, DOM and accessibility snapshots, and network metadata.
Secret referencesA recognised credential field is stored as a named reference such as ${secret.ADMIN_PASSWORD}. The typed value is never captured.

Capture profiles

The privacy profile inherited from the project decides how much of the page is retained. Strict is the default and is designed for routine testing; Diagnostic keeps more context and still enforces the sensitive-field controls. Neither profile can be weakened into capturing credential headers, secret-bearing fills, or unmasked sensitive screenshots — those are filtered at collection, not at display.

From capture to suite

Stopping the capture compiles it. WeftKit turns the timeline into an ordered suite with explicit waits and assertions, then stores it as a file in your project. From the studio you can open the compiled suite directly; the recording itself is kept as its own report so you can always compare the suite against what was demonstrated.

LimitationPage-level capture does not include browser chrome or native prompts. Native browser-window video is a declared coverage gap, and the app states it in the run report rather than implying full-screen capture.
Next: Suites & steps