Capture and generation updates
Use Capture to record a working journey, correct its intent, and generate code that passes replay before you keep it.
Browser recording and codegen
- What it does
- Records browser interactions and generates maintainable SHAFT steps.
- Why use it
- Turn a working browser journey into reviewable code.
- Configure
- Start Capture from IntelliJ, MCP, or CLI against the target browser session.
- Use it
- Record the journey, stop the session, review locators, then replay before committing.
Browser API recording
- What it does
- Captures browser network calls and produces API-oriented replay blocks.
- Why use it
- Reuse observed requests without manually reconstructing their method, path, and payload.
- Configure
- Start Capture with API recording enabled before exercising the browser journey.
- Use it
- Review redaction and generated requests, then replay them in a focused test.
Native mobile API capture
- What it does
- Records API traffic associated with an active native mobile session.
- Why use it
- Create API replay evidence for mobile journeys.
- Configure
- Start the mobile API capture tool while the supported mobile engine is active.
- Use it
- Exercise the journey, stop capture, then review and replay generated code blocks.
Recorder assertions and step editing
- What it does
- Adds assertion mode, locator picking, record-at-target, and step editing to the recorder workbench.
- Why use it
- Correct intent and locators before generated code reaches the project.
- Configure
- Open the Capture workbench and select recording or assertion mode.
- Use it
- Pick a target, adjust the step, then replay the edited scenario.
Scenario-to-code generation
- What it does
- Converts a reviewed Capture scenario into SHAFT test code.
- Why use it
- Keep generated code tied to an explicit, editable journey.
- Configure
- Save the reviewed scenario and choose the documented code generation route.
- Use it
- Generate, compile, and replay the test before keeping it.
Verified test-ID replay
- What it does
- Prefers unique author-written test IDs and verifies generated steps through replay.
- Why use it
- Avoid committing locators that looked plausible but did not reproduce the journey.
- Configure
- Expose stable unique test IDs in the application where semantic locators are insufficient.
- Use it
- Replay generated code and keep it only after the target journey passes.
Open the local Capture workflow through its documented client:
/record
