Perform it once. Keep it as a test forever.
Recording Studio turns a manual browser session into a structured, reusable TestHub scenario. Show the flow instead of describing it.
From manual session to reusable scenario in five steps
- 01
Start a recording session
Launch Recording Studio against any application registered in TestHub. A real browser opens on your app, connected to the recorder.
- 02
Perform the journey manually
Navigate, click, fill forms, and submit exactly as a user would. Every meaningful action is captured as a candidate step: navigations, clicks, and typed input.
- 03
Mark assertions as you go
Point at an element or text that should be verified and it becomes an expectation step. Assertions are captured in context, while you are looking at the page.
- 04
Review the compiled scenario
The recording is compiled into the same canonical scenario vocabulary as every other TestHub test: explicit steps, grounded selectors, and clear assertions. Review and adjust before saving.
- 05
Save it and run it anywhere
The recorded scenario joins your library like any other: schedulable, runnable locally or in CI, parameterizable with environment values, and maintainable as your application evolves.
Pick the right path for each flow
Recording Studio joins two existing authoring paths. Everything lands in the same structured scenario format, so teams can mix approaches freely.
Agentic authoring
Describe the intent and let an agent write the scenario. Best for teams already working with AI coding agents.
Scenario discovery
Let TestHub propose what to test from your codebase. Best for building coverage systematically.
Recording Studio
Perform the flow once and keep it. Best for complex journeys and for QA engineers who know the application by heart.
The fastest path from a working flow to a working test
Show, don't describe
Some flows are faster to perform than to explain. Recording skips the prompt-and-revise loop entirely.
Structured, not brittle
Recordings compile into the same structured scenario format as agent-authored tests, not opaque playback scripts.
An alternative to purely agentic authoring
For teams that want full manual control over what becomes a test, Recording Studio is the hands-on path.
Same destination
However a scenario is created, it ends up in the same library: reviewed, versioned, schedulable, and CI-ready.
Explore all TestHub capabilities · Currently viewing: TestHub Recording Studio
Want Recording Studio on your application?
Request a walkthrough and tell us you are interested in Recording Studio. We will keep you posted as it ships.
Part of SolidX