in a local test environment, use an adapter CustomChromeDriver to work also in dockerized dev environments

This commit is contained in:
Axel Uhl
2025-08-15 09:53:40 +02:00
parent 41c269352f
commit 748b96752d
2 changed files with 26 additions and 1 deletions
@@ -91,9 +91,13 @@
<driver-definition class="org.openqa.selenium.firefox.FirefoxDriver">
</driver-definition>
-->
<!-- -->
<!--
<driver-definition class="org.openqa.selenium.chrome.ChromeDriver">
</driver-definition>
-->
<!-- -->
<driver-definition class="com.sap.sailing.selenium.core.CustomChromeDriver">
</driver-definition>
<!-- -->
<!--
<driver-definition class="org.openqa.selenium.ie.InternetExplorerDriver">
@@ -0,0 +1,21 @@
package com.sap.sailing.selenium.core;
import org.openqa.selenium.Capabilities;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.chrome.ChromeDriverService;
import org.openqa.selenium.chrome.ChromeOptions;
public class CustomChromeDriver extends ChromeDriver {
public CustomChromeDriver(Capabilities capabilities) {
super(ChromeDriverService.createDefaultService(), buildOptions());
}
private static ChromeOptions buildOptions() {
ChromeOptions options = new ChromeOptions();
options.addArguments("--no-sandbox");
options.addArguments("--disable-dev-shm-usage");
options.addArguments("--disable-gpu");
options.addArguments("--remote-debugging-port=9222");
return options;
}
}