sg-record

To record browser interactions into YAML test manifests, you run a recorder against your target URL that captures user steps via a floating toolbar and exports ready-to-play ShipGuard YAML files under visual-tests/manifests.

Yes, you need Playwright installed locally to record browser actions. The recorder requires the Playwright runtime to bootstrap the recording session, capture interactions, and manage persistent auth state when requested.

A browser action recorder generates reproducible visual regression tests by capturing deterministic user steps through a floating toolbar and translating them directly into structured ShipGuard YAML manifests for the automation pipeline.

Yes, you can persist authentication state when recording browser automation manifests. The recorder lifecycle bootstrap manages auth state during the session, ensuring your exported YAML tests are replay-ready for authenticated visual regression scenarios.

The best way to automate test scripting without manual YAML coding is using a macro recorder that captures browser interactions through a floating toolbar and automatically translates them into deterministic ShipGuard YAML manifests for visual regression pipelines.

Recorded browser manifests may not integrate with your visual regression pipeline if they are not placed under the visual-tests/manifests directory or if the output lacks deterministic formatting required by downstream visual review pages and run environments.