playwright-interactive

To maintain persistent Playwright sessions for UI debugging, use a js_repl-enabled runtime to preserve browser and Electron handles across code changes, avoiding repeated toolchain startup overhead while iterating on local web or desktop applications.

Taking normalized screenshots for QA verification involves running a separate visual verification pass that applies CSS-pixel screenshot normalization, ensuring reliable visual signoff and consistent functional checks across different viewport and mobile modes.

Yes, you can debug an Electron app without restarting the toolchain by launching the Electron entry within a persistent Playwright session, preserving window handles across iterations to rapidly verify behavior and capture QA evidence.

Reloading versus relaunching a browser depends on mode-aware workflow rules: reload preserves the current browser state for minor code changes, while relaunching resets the session entirely when significant structural updates require a fresh application state.

To run iterative functional and visual QA checks with Playwright, you need Playwright installed and a js_repl-enabled runtime in your project workspace to start a persistent session, open the target URL, and execute the bootstrap cell.