How do you set up a maintainable Selenium project?

A clean layout makes the suite easier to grow. I keep tests under src/test/java, page objects in a pages package, configuration and driver creation in support, and test data in resources. Versions are pinned in one place so local and CI runs use the same stack.

<dependency>
  <groupId>org.seleniumhq.selenium</groupId>
  <artifactId>selenium-java</artifactId>
  <version>4.25.0</version>
  <scope>test</scope>
</dependency>

<dependency>
  <groupId>org.testng</groupId>
  <artifactId>testng</artifactId>
  <version>7.10.2</version>
  <scope>test</scope>
</dependency>

• Tests contain intent and assertions; page objects contain locators and interactions
• A driver factory reads browser, headless and remote settings from configuration
• Selenium Manager resolves drivers by default, so avoid committing driver binaries
• Use environment variables for credentials and grid URLs rather than hard-coded secrets
• Fail fast at startup if the browser or grid is unavailable

For remote runs, the same project should point at a Grid URL instead of a local browser. That means driver creation must be centralised; tests should never call new ChromeDriver directly.