Currently, switching from the default browser (HtmlUnit) to one of the other browsers is a tedious process. I need to not only change the value of the selenium.browser.name or selenium.browser.caps setting, but I also need to change the driver plugin specified in the com.nordstrom.automation.selenium.DriverPlugin resource file in src/test/resources/META-INF/services and add the corresponding dependencies to pom.xml. I may be able to forego this hassle by adding profiles similar to those of the local-grid-parent project.
In addition to the indicated service loader configuration file, the active plugins can be specified via the selenium.grid.plugins setting. This means that all of the configuration needed to activate an alternate browser can be specified in pom.xml.
sbabcoc
commented
1 year ago
Currently, switching from the default browser (HtmlUnit) to one of the other browsers is a tedious process. I need to not only change the value of the
selenium.browser.nameorselenium.browser.capssetting, but I also need to change the driver plugin specified in thecom.nordstrom.automation.selenium.DriverPluginresource file in src/test/resources/META-INF/services and add the corresponding dependencies to pom.xml. I may be able to forego this hassle by adding profiles similar to those of the local-grid-parent project.In addition to the indicated service loader configuration file, the active plugins can be specified via the
selenium.grid.pluginssetting. This means that all of the configuration needed to activate an alternate browser can be specified in pom.xml.