Start a new suite
Generate a Maven project, then run its first test with the checked-in command.
Generate a project
Release decisions backed by inspectable evidence.
Run one Java project across web, mobile, API, database, and CLI. Keep native engine control, then connect Capture, Doctor, Heal, and MCP when they add evidence.
- Generate project
mvn test- Inspect report
From intent to reviewable Java and evidence.
Use evidence to keep engineers in control and give delivery leaders a reviewable release signal.
Evidence first
Failed Allure or trace evidence classified cause review-only remediation guidance
Run doctor_analyze_failed_allure or doctor_analyze_trace to classify evidence before reviewing a proposal.
Doctor output
classification: locator
evidence: failed Allure action and trace context
next step: review remediation guidance
Model choice remains with the MCP client. Tests remain ordinary Java. Proposals do not silently edit, approve, or merge.
Start from the job in front of you
For engineers, preserve native Java control. For delivery leaders, make release evidence easy to inspect.
Migrate an existing suite
Upgrade supported Selenium, Appium, REST Assured, or older SHAFT projects in controlled steps.
Read upgrade guideAdd another testing surface
Keep web, mobile, API, database, and CLI checks in one Java project and evidence model.
Explore surfacesDiagnose a failed run
Use failed Allure or trace evidence to classify a cause before reviewing a remediation proposal.
Review diagnosis flowOne evidence model across five test surfaces
Start with the native engine. Keep the evidence and Java suite in one place.
Web SHAFT snippet
SHAFT.GUI.WebDriver driver = new SHAFT.GUI.WebDriver();
driver.browser().navigateToURL("https://example.com");
driver.element().click(By.id("submit"));
Native engine
Appium
Touch actions, device context, screenshots, and native trace evidence.
Read mobile guideMobile SHAFT snippet
driver.touch().tap(SHAFT.GUI.Locator.accessibilityId("Views"));
driver.assertThat().element(By.id("screen")).exists().perform();
API SHAFT snippet
SHAFT.API api = new SHAFT.API(apiFixtureUrl);
api.get("users").performRequest();
Native engine
JDBC
Connection target, query result, validation, and report evidence.
Read database guideDatabase SHAFT snippet
SHAFT.DB database = new SHAFT.DB("jdbc:h2:mem:test");
ResultSet rows = database.executeSelectQuery("SELECT 1");
Native engine
Local, Docker, SSH
Commands, captured output, and validation in the same report.
Read cli guideCLI SHAFT snippet
String output = SHAFT.CLI.terminal()
.performTerminalCommand("echo Hello SHAFT");
Trust, performance, and community
SHAFT releaseInspect SHAFT 10.3.20260727 releases and changes.Java baselineBuild the current release on Java 25.MIT licenseUse and inspect SHAFT under a permissive open-source license.CI gateReview the same pull-request checks used by the project.Security policyCheck supported versions and private disclosure guidance.Release historyInspect published versions, dates, and changes.Selenium ecosystemFind SHAFT in Selenium’s official ecosystem directory.
Start with a project. Keep the evidence.
Generate a focused starter, examine the documentation, or follow development on GitHub.