playwright-interactive

To maintain a persistent Playwright session for continuous UI debugging, you initialize the interactive skill to keep browser or Electron handles active across iterations without restarting the toolchain. This allows you to quickly iterate through UI changes and validate them in real-time.

Yes, you can debug an Electron app using Playwright without restarting the process by utilizing persistent sessions. This skill manages native-window Electron handles specifically to support continuous functional and visual QA without interrupting your debugging workflow.

You need the Playwright dependency, and optionally Chromium or Electron, to perform visual QA. Chromium is utilized for standard web browser debugging, while Electron support is included for debugging native-window desktop applications.

The best way to handle different Playwright session types for web, mobile, native-window, and Electron testing is through dedicated session management. This skill provides specific setup commands and workflow instructions to configure and maintain each session type independently.

Your browser debugging session closes during UI iterations because the toolchain restarts. Using persistent Playwright sessions prevents this by maintaining the same browser handles across iterations, enabling continuous functional and visual QA without interruptions.