如何通过Java和Selenium在ChromeDriver启动后切换到Electron应用进行交互

Great question—let's break this down clearly. The short answer is: ChromeDriver can't directly switch to an Electron app that pops up after clicking a link in Chrome. Here's why, and how to solve your testing scenario:

Why you can't switch directly #

ChromeDriver is built exclusively to control the Chrome browser process it initializes. Even though Electron uses a Chromium engine, it runs as a completely separate, independent process with its own WebDriver endpoint. There's no built-in way to "switch" your existing ChromeDriver session over to this new Electron process.

Solution 1: Launch the Electron app directly with WebDriver #

If your test flow allows it (or you can adjust it), skip the Chrome step entirely and launch the Electron app directly using ChromeDriver. Electron has native WebDriver support—you just need to point ChromeDriver to your Electron binary and enable debugging.

Here's how to modify your existing startDriver() method to handle both Chrome and Electron:

public static WebDriver startDriver(boolean launchElectron) {
    String projectLocation = System.getProperty("user.dir");
    WebDriver driver;

    if (launchElectron) {
        // Path to your Electron app binary (adjust paths for your OS)
        String electronBinaryPath;
        if (OSValidator.isMac()) {
            electronBinaryPath = "/path/to/your/ElectronApp.app/Contents/MacOS/ElectronApp";
        } else if (OSValidator.isWindows()) {
            electronBinaryPath = "C:\\path\\to\\your\\ElectronApp.exe";
        } else {
            electronBinaryPath = "/path/to/your/ElectronApp";
        }

        ChromeOptions options = new ChromeOptions();
        // Point ChromeDriver to the Electron binary instead of Chrome
        options.setBinary(electronBinaryPath);
        // Enable remote debugging (required for WebDriver connection)
        options.addArguments("--remote-debugging-port=9222");
        // Add sandbox disable flag (common for Electron testing on some OS)
        options.addArguments("--no-sandbox");

        driver = new ChromeDriver(options);
    } else {
        // Your existing ChromeDriver initialization logic
        if (OSValidator.isMac()) {
            System.setProperty("webdriver.chrome.driver", projectLocation + "/chromedriver_mac");
        } else if (OSValidator.isWindows()) {
            System.setProperty("webdriver.chrome.driver", projectLocation + "/chromedriver.exe");
        } else {
            System.setProperty("webdriver.chrome.driver", projectLocation + "/chromedriver_linux");
        }

        if (System.getProperty("app.env") != null) {
            System.setProperty("webdriver.chrome.verboseLogging", "true");
        }

        ChromeOptions options = new ChromeOptions();
        options.addArguments("start-maximized");
        options.addArguments("disable-infobars");
        options.addArguments("--disable-extensions");
        options.addArguments("--window-size=1920x1080");
        options.addArguments("--disable-cache");
        options.addArguments("--disable-application-cache");
        options.addArguments("--disk-cache-size=0");
        options.addArguments("--disable-gpu");
        options.addArguments("--disable-dev-shm-usage");
        options.addArguments("--dns-prefetch-disable");
        options.addArguments("--disable-notifications");
        options.addArguments("disable-infobars");

        LoggingPreferences logPrefs = new LoggingPreferences();
        logPrefs.enable(LogType.BROWSER, Level.ALL);
        options.setCapability(CapabilityType.LOGGING_PREFS, logPrefs);
        options.setPageLoadStrategy(PageLoadStrategy.NORMAL);

        driver = new ChromeDriver(options);
        driver.manage().window().maximize();
    }

    return driver;
}

Solution 2: Handle Chrome → Electron flow with two separate sessions #

If you must first interact with Chrome (click the link that launches Electron), use two separate WebDriver sessions:

1. First session: Control Chrome, perform actions until you click the link to launch Electron.
2. Second session: Connect ChromeDriver to the already-running Electron app (requires Electron to launch with debugging enabled).

Step 1: Ensure Electron launches with remote debugging #

Configure the link/trigger that launches your Electron app to pass the --remote-debugging-port=9222 argument. You can set this in your Electron app's build config or add it to the command line when the app is invoked from Chrome.

Step 2: Connect a new session to Electron #

After clicking the link in Chrome, wait for Electron to fully launch, then initialize a new WebDriver session pointing to the debugging port:

// First, use ChromeDriver to interact with Chrome and trigger Electron
WebDriver chromeDriver = startDriver(false);
// ... perform actions in Chrome, click the link that opens Electron ...
Thread.sleep(3000); // Wait for Electron to finish launching (adjust timing as needed)

// Create a new session for the Electron app
ChromeOptions electronOptions = new ChromeOptions();
electronOptions.addArguments("--remote-debugging-port=9222");
WebDriver electronDriver = new ChromeDriver(electronOptions);

// Now interact with the Electron app using electronDriver
electronDriver.findElement(By.id("electron-app-element")).click();

Critical Tips #

• Version Match: Use a ChromeDriver version that matches the Chromium version bundled in your Electron app (check Electron's documentation to find this version). Mismatched versions will cause compatibility errors.
• Test Consistency: For reliable testing, package your Electron app with debugging enabled by default in test environments.

内容的提问来源于stack exchange，提问作者FearghalQA