Selenium Boot Migrator
CLI · Maven + GradleMove an existing Selenium project over, safely
Already have Selenium tests? Do not rewrite them. The Migrator scans an existing Selenium Java project, reports what maps onto Selenium Boot and what needs a human, and can write a migrated copy with the mechanical changes applied.
$ java -jar selenium-boot-migrator.jar analyze ./my-selenium-projectEarly release. Download selenium-boot-migrator.jar from GitHub Releases; it is a CLI, not a dependency. Needs Java 17+.
Capabilities
What it does
Read-only analysis
analyze reports counts per rule, what maps cleanly, what needs review, and an estimated confidence. It never touches your source.
Migrate into a copy
migrate writes a separate directory and applies only mechanical rules; your original project is never edited.
Maven and Gradle
Rewrites selenium-java in pom.xml, build.gradle(.kts), and Gradle version catalogs, keeping the alias so existing references still resolve.
CI-friendly
JSON output and a --fail-under threshold turn the confidence estimate into a pipeline gate.
Runs locally
Your source stays on your machine. The same analysis is exposed as a migrate tool in the MCP server.
Keep your test code. Delete the plumbing.
Add one dependency and focus on testing — not framework engineering.
<dependency>
<groupId>io.github.seleniumboot</groupId>
<artifactId>selenium-boot</artifactId>
<version>3.8.0</version>
</dependency>Or start from a working project:use the starter template ↗