playwright

Persistent state automation maintains your browser session, element references, and storage across commands. Start by navigating to a URL, snapshot elements for refs, then reuse those refs in subsequent interactions like clicks and form fills without reinitializing the browser each time.

Yes. Playwright enables screenshot and PDF generation at any point in your test flow. After navigating and interacting with page elements, call screenshot or PDF capture to document UI state, then continue with additional steps or close the browser.

Element discovery works through snapshots that capture element references into a persistent JSON file. Use those refs in subsequent commands to click, type, or fill forms without re-querying the DOM, speeding up multi-step workflows.

Structure tests as sequential commands reusing a single browser instance and persistent element refs. Navigate pages, snapshot new elements as needed, interact via stored refs, capture verification screenshots or PDFs, and maintain context across the entire flow in one session.

No. Persistent browser state stores your session, element refs, and storage state in JSON files (.browser-state.json, .element-refs.json, .storage-state.json), eliminating reinit overhead and allowing commands to chain without setup repetition.

Element refs captured once during a snapshot are reused across subsequent commands via stored JSON references. This eliminates repeated DOM queries and selector maintenance, letting you focus on interaction logic instead of element discovery on every step.