Selenium WebDriver能否测试注入页面的WebExtension？是否只能用SikuliX？

First off, no—you don’t have to rely solely on SikuliX, but it’s absolutely a top-tier choice for your specific scenario. Let’s break down your questions and actionable solutions:

Alternatives to SikuliX for Chrome* Page Testing #

While WebExtensions are blocked from injecting JS into chrome:// pages (a core Chrome security restriction), there are other tools/methods to complement or replace SikuliX depending on your testing goals:

• Chrome DevTools Protocol (CDP): Pair CDP with Selenium to interact directly with Chrome’s internal pages and extensions. You can trigger extension commands, inspect UI elements in chrome:// pages, or simulate actions without relying on DOM injection.
• Chrome Extension Testing APIs: If you’re building a Chrome-only extension, the chrome.test API lets you write unit/integration tests that run within the extension context—though it won’t help with visual UI testing of chrome:// pages.
• Playwright: Similar to Selenium but with native, better support for extensions and CDP. It handles extension popups, background scripts, and can interact with chrome:// pages via CDP commands seamlessly.

Why SikuliX Is Perfect for Your Use Case #

You’re spot-on about SikuliX’s strengths—it fills a unique gap when DOM access is off-limits:

• Visual UI Validation: It verifies button badges, CSS styling, and layout correctness by comparing screen captures to expected visuals—something DOM-only testing can’t do.
• Robust User Simulation: Using image recognition, it mimics real human behavior (clicking, typing, navigating) exactly, making it ideal for end-to-end tests that need to interact with chrome:// pages or extension UI elements without DOM hooks.

Fixing Your Hotkey send_keys Issue #

The problem with driver.find_element_by_tag_name('body').send_keys(...) usually boils down to one of these common pitfalls:

1. Incorrect focus: The body element might not have active focus, so Chrome or your extension doesn’t register the keystrokes.
2. Conflicting shortcuts: If your extension’s hotkey overlaps with a built-in Chrome shortcut, Chrome will intercept it before your extension can.
3. Syntax errors: You might not be using Selenium’s Keys class correctly for modifier keys.

Try these targeted fixes:

Use Selenium’s ActionChains for Precise Key Simulation #

This method ensures proper modifier key handling and focus:

from selenium.webdriver.common.action_chains import ActionChains
from selenium.webdriver.common.keys import Keys

# Ensure the browser window is focused first
driver.switch_to.window(driver.current_window_handle)

# Build and execute your hotkey combination (example: Ctrl+Shift+K)
actions = ActionChains(driver)
actions.key_down(Keys.CONTROL)\
       .key_down(Keys.SHIFT)\
       .send_keys('k')\
       .key_up(Keys.SHIFT)\
       .key_up(Keys.CONTROL)\
       .perform()

Trigger Extension Commands Directly (If Applicable) #

If your hotkey is tied to a command in your manifest.json (under the commands field), use CDP to trigger it directly without simulating keystrokes:

# Example using Selenium + CDP to run an extension command
driver.execute_cdp_cmd("commands.execute", {"name": "your-extension-command-name"})

Final Recommendation #

If your testing leans heavily on chrome:// page interactions or visual validation, SikuliX is your most reliable tool. For testing extension behavior on regular web pages, combine Selenium/Playwright with CDP for more control. For hotkey issues, prioritize ActionChains or direct CDP command execution over sending keys to the body element.

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