Fixing Java tests

[diemol]

PR Type

Bug fix, Tests

---

Description

• Updated Chrome extension testing to use BiDi WebExtension API

  • Replaced deprecated .crx file-based extension loading
  • Implemented new WebExtension, ExtensionPath, and InstallExtensionParameters classes
  • Added BiDi and remote debugging pipe configuration

• Fixed Edge driver log assertion to match actual output

  • Changed expected log message from "Starting Microsoft Edge WebDriver" to "Starting msedgedriver"

• Cleaned up wildcard imports in EdgeTest for better code clarity

---

Diagram Walkthrough

flowchart LR
  A["Chrome Extension Test"] -->|Replace deprecated| B["BiDi WebExtension API"]
  B -->|Use new classes| C["ExtensionPath & InstallExtensionParameters"]
  D["Edge Driver Logs"] -->|Fix assertion| E["Updated log message"]
  F["Import statements"] -->|Expand wildcards| G["Explicit imports"]

Loading

File Walkthrough

Relevant files

Bug fix

ChromeTest.java Migrate Chrome extension test to BiDi WebExtension API      examples/java/src/test/java/dev/selenium/browsers/ChromeTest.java Added imports for BiDi WebExtension API classes (ExtensionPath, InstallExtensionParameters, WebExtension) Refactored extensionOptions() test to use BiDi WebExtension API instead of deprecated .crx file loading Enabled BiDi and added remote debugging pipe arguments to ChromeOptions Changed extension path from .crx file to directory-based path Instantiated WebExtension object and used new parameter-based installation method +12/-5    EdgeTest.java Fix Edge log assertion and expand wildcard imports              examples/java/src/test/java/dev/selenium/browsers/EdgeTest.java Expanded wildcard import org.openqa.selenium.logging.* into explicit individual imports Updated log assertion in logsToConsole() test to expect "Starting msedgedriver" instead of "Starting Microsoft Edge WebDriver" +5/-2

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No audit logs: The newly added extension installation and browser configuration actions add no audit logging, but as this is a test file it may not require audit trails. Referred Code options.enableBiDi(); options.addArguments("--remote-debugging-pipe"); options.addArguments("--enable-unsafe-extension-debugging"); driver = new ChromeDriver(options); Path path = Paths.get("src/test/resources/extensions/selenium-example"); WebExtension extension = new WebExtension(driver); ExtensionPath extensionPath = new ExtensionPath(path.toString()); InstallExtensionParameters parameters = new InstallExtensionParameters(extensionPath); extension.install(parameters); driver.get("https://www.selenium.dev/selenium/web/blank.html"); WebElement injected = driver.findElement(By.id("webextensions-selenium-example")); Assertions.assertEquals( "Content injected by webextensions-selenium-example", injected.getText()); Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Missing error handling: New BiDi extension installation and driver initialization have no try/catch or assertions for failures, which may be acceptable in test context but lacks explicit handling. Referred Code options.enableBiDi(); options.addArguments("--remote-debugging-pipe"); options.addArguments("--enable-unsafe-extension-debugging"); driver = new ChromeDriver(options); Path path = Paths.get("src/test/resources/extensions/selenium-example"); WebExtension extension = new WebExtension(driver); ExtensionPath extensionPath = new ExtensionPath(path.toString()); InstallExtensionParameters parameters = new InstallExtensionParameters(extensionPath); extension.install(parameters); Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: External input trust: The test enables BiDi and installs an extension from a path without validating source or handling potential security implications, though this may be acceptable for controlled tests. Referred Code options.enableBiDi(); options.addArguments("--remote-debugging-pipe"); options.addArguments("--enable-unsafe-extension-debugging"); driver = new ChromeDriver(options); Path path = Paths.get("src/test/resources/extensions/selenium-example"); WebExtension extension = new WebExtension(driver); ExtensionPath extensionPath = new ExtensionPath(path.toString()); InstallExtensionParameters parameters = new InstallExtensionParameters(extensionPath); extension.install(parameters); Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Ensure extension is uninstalled after test Capture the extension ID from extension.install() and use it to uninstall the extension in a finally block to ensure test isolation and prevent state leakage. examples/java/src/test/java/dev/selenium/browsers/ChromeTest.java [69-78] -Path path = Paths.get("src/test/resources/extensions/selenium-example"); WebExtension extension = new WebExtension(driver); -ExtensionPath extensionPath = new ExtensionPath(path.toString()); -InstallExtensionParameters parameters = new InstallExtensionParameters(extensionPath); -extension.install(parameters); +String extensionId = null; +try { + Path path = Paths.get("src/test/resources/extensions/selenium-example"); + ExtensionPath extensionPath = new ExtensionPath(path.toString()); + InstallExtensionParameters parameters = new InstallExtensionParameters(extensionPath); + extensionId = extension.install(parameters); -driver.get("https://www.selenium.dev/selenium/web/blank.html"); -WebElement injected = driver.findElement(By.id("webextensions-selenium-example")); -Assertions.assertEquals( - "Content injected by webextensions-selenium-example", injected.getText()); + driver.get("https://www.selenium.dev/selenium/web/blank.html"); + WebElement injected = driver.findElement(By.id("webextensions-selenium-example")); + Assertions.assertEquals( + "Content injected by webextensions-selenium-example", injected.getText()); +} finally { + if (extensionId != null) { + extension.uninstall(extensionId); + } +} Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies a potential test isolation issue by not uninstalling the extension, which could lead to flaky tests. The proposed try-finally block is a robust solution for ensuring cleanup.	Medium
Update

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	9a6ba01
🔍 Latest deploy log	https://app.netlify.com/projects/selenium-dev/deploys/692571840280210008d6f82b
😎 Deploy Preview	https://deploy-preview-2542--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.