Repository navigation
Remove unused webdriver.chrome.driver property and related configuration from pom.xml #62
Closed as not planned
Description
Summary
The webdriver.chrome.driver property and related configuration in pom.xml appear to be unused and can be safely removed.
Details
Tests use WebDriverManager.chromedriver().setup() to manage the Chrome driver and create instances with new ChromeDriver(). The property defined in the <properties> block and passed as a system property in the integration-tests profile via <systemPropertyVariables> is never read by test code. Additionally, the drivers directory referenced by this property does not exist in the repository.
Proposed Cleanup
Remove the following from pom.xml:
- The property definition:
<webdriver.chrome.driver>${drivers.dir}/chromedriver</webdriver.chrome.driver>- The system property variable block in the
integration-testsprofile:
<systemPropertyVariables>
<!-- Pass location of downloaded webdrivers to the tests -->
<webdriver.chrome.driver>${webdriver.chrome.driver}</webdriver.chrome.driver>
</systemPropertyVariables>References
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
javier-godoy commentedon Apr 28, 2026
The drivers directory is not commited to the repository:
ChatAssistant/.gitignore
Line 14 in 8bfc64e
Drivers are managed through this dependency
ChatAssistant/pom.xml
Lines 167 to 171 in 8bfc64e
The driver executable must be included in the operating system PATH or be given to the test using a driver-specific system Java property: Google Chrome: webdriver.chrome.driver (from https://vaadin.com/docs/latest/flow/testing/end-to-end/installing-webdrivers#adding-webdriver-to-system-path)