Release decisions backed by inspectable evidence.

Run across web, mobile, API, database, and CLI. Keep the evidence close to the decision it informs.

Create new project Explore documentation Star on GitHub

Real SHAFT execution. Open the report evidence and inspect it.

Verify the project before you adopt it

MIT licenseUse and inspect SHAFT under a permissive open-source license.Build historyReview the same pull-request gate 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.Peer BonusReview Google’s 2023 open-source recipient announcement.Execution evidenceInspect passed, failed, and visual evidence from real SHAFT runs.

Evidence that survives scrutiny

Steps, attachments, diagnostics, and visual checks remain inspectable after the run.

Real SHAFT Allure report showing a passed visual-validation test, expanded steps, and an opened screenshot attachment. — **Passed steps, attached proof**Inspect actions and captured evidence in the same run.

Real SHAFT Allure report showing a failed browser action with its screenshot and exception evidence. — **Failure context, ready to inspect**Move from the failed action to its screenshot and trace without reconstructing the run.

Visual evidence beside the resultReview the expected image, actual image, and deterministic OpenCV difference together.

Useful at the keyboard and in the release room

For engineers

Keep native Java control while SHAFT owns repeatable suite mechanics.

Run browser, mobile, API, database, and CLI checks together.
Move lifecycle, synchronization, screenshots, and logs out of test intent.
Start debugging with evidence already attached.

For delivery leaders

Make automation results inspectable before they inform a release.

Use one onboarding path for new and existing projects.
Review steps, screenshots, traces, and diagnostics together.
Audit license, releases, CI, security, and support from primary sources.

Choose the shortest path to evidence

First run

Generate a SHAFT project

Choose test surfaces and download a ready-to-run project.

Open generator

Quick start

Run your first test

Move from setup to an evidence report through one short guide.

Read quick start

Migration

Upgrade an existing suite

Adopt SHAFT by test surface without rewriting everything at once.

Plan the upgrade

Expansion

Add another test surface

Bring mobile, API, database, CLI, or Grid evidence into the same run.

Compare surfaces

Agentic

Connect MCP after the basics

Expose Capture, Doctor, Heal, and browser tools after the project compiles.

Connect MCP

One evidence model across five test surfaces

Web GUI

Selenium + Playwright

Actions, synchronization, locators, screenshots, and report steps.

Mobile GUI

Appium

Android, iOS, mobile web, emulators, real devices, and clouds.

API

REST Assured

Requests, schemas, authentication, assertions, and payload evidence.

Database

JDBC

Connections, queries, updates, and result validation.

CLI

Local, Docker, SSH

Commands, containers, remote shells, files, and captured output.

Move from observation to maintainable automation

SHAFT Capture showing locator inspection and captured browser evidence. — **Capture the real interaction**Record browser activity, inspect locators, and retain evidence for generation.

SHAFT IntelliJ Assistant showing agentic project guidance inside the IDE. — **Keep guidance in the IDE**Connect project context, MCP tools, and focused assistance where engineers work.

Write intent. Keep control.

SHAFT reduces repeated lifecycle and evidence plumbing without hiding the native engines beneath it.

Driver lifecycle, waits, retries, and synchronization
Screenshots, logs, steps, and attachments
Configuration and data isolation
Allure evidence that Doctor and Heal can inspect

A readable SHAFT test
driver.browser().navigateToURL(appUrl);
driver.element().type(username, user);
driver.element().click(signIn);
driver.element().assertThat(home).exists();

Adopt without a rewrite mandate

Move an existing suite

Adopt SHAFT by surface. Keep useful tests and migrate in controlled steps.

Read migration guidance

Run where your team builds

Use the same Maven project on developer machines and CI.

Review first-run guidance

Keep native-tool access

Use underlying automation APIs directly when a case needs them.

Compare modules

Evaluate stewardship

Inspect project terms, releases, security, CI, and public support.

Review project evidence

Evidence improves the next run

ExecuteRun web, mobile, API, database, and CLI checks.
CollectCapture screenshots, logs, requests, responses, and data facts.
ReportKeep the timeline and attachments in Allure.
DiagnoseUse the report and Doctor to understand the failure path.
ImproveApply a deterministic fix; use Heal when evidence supports recovery.

Visual comparison is deterministic. AI-assisted Heal is a separate recovery capability; Doctor explains evidence-backed failure paths; MCP connects those tools to supported assistants.

Start with a project. Keep the evidence.

Generate a focused starter, examine the documentation, or follow development on GitHub.