Move an existing suite
Use the existing-project path to update dependencies and adopt SHAFT by test surface. You do not need to rewrite every test at once.
Read the migration path
SHAFTio.github.shafthq : shaft-engine
Reliable automation evidence for every release.
One Java framework for web, mobile, API, database, and CLI testing. Keep native tool control while SHAFT standardizes synchronization, lifecycle, and report evidence.
No account. No payment details. Choose your surfaces, download a ready-to-run Maven project, and produce your first evidence report.
Real SHAFT reportRun health across launches
Verify before you adopt
Every signal below links to its primary source.
MIT licenseUse, inspect, and adapt the framework under a permissive open-source license.Maven CentralPublished Java artifacts are available from the standard public package repository.Build historyInspect the project pull-request gate and its recent results on GitHub Actions.Security policyReview supported versions and the private vulnerability-reporting path.Release historyReview tagged releases, dates, and change notes before you upgrade.Selenium ecosystemSHAFT is listed in Selenium’s official ecosystem directory of test frameworks.Google Open Source Peer BonusProject maintainer Mohab Mohie appears in Google’s 2023 peer-bonus recipient announcement.Community supportAsk implementation questions in the public SHAFT Slack community.
One evidence model
Technical control for engineers. Inspectable results for leaders.
For engineers
Keep native Java control while SHAFT owns repeatable suite mechanics.
- Use Selenium, Playwright, Appium, REST Assured, JDBC, and CLI from one framework.
- Move waits, lifecycle, screenshots, logs, and report steps out of test intent.
- Start a failure investigation with artifacts attached to the run.
For delivery leaders
Make the automation result inspectable before it informs a release decision.
- Use one onboarding path for new projects, migrations, and additional test surfaces.
- Review steps, screenshots, logs, and diagnostics in the same evidence trail.
- Check license, releases, CI history, security, and community support from primary sources.
Adopt in controlled steps
Start with the path that matches your team.
Generate a project, run it, inspect the evidence, then add only what your suite needs.
Canonical engine coordinate
<dependency>
<groupId>io.github.shafthq</groupId>
<artifactId>shaft-engine</artifactId>
<version>10.3.20260727</version>
</dependency>
First runGenerate a SHAFT projectChoose your test surfaces and download a ready-to-run Maven project.Open generatorQuick startRun your first testFollow the short path from project setup to an evidence report.Read quick startMigrationUpgrade an existing projectMove Selenium, Appium, REST Assured, Cucumber, or older SHAFT suites in controlled steps.Plan the upgradeExpansionAdd coverage beyond the browserAdd mobile, API, CLI, database, or Grid checks when the product needs them.Compare surfacesAgenticConnect MCP after the basicsExpose browser, Capture, Doctor, and Heal tools after the project compiles.Connect MCP
Testing surfaces
One framework. Five testing surfaces.
Expand coverage without changing the project’s configuration, lifecycle, or reporting model.
Web GUIBrowser actions, synchronization, locators, screenshots, logs, and report steps.Selenium + Playwright
Mobile GUIAndroid, iOS, mobile web, Flutter, emulators, real devices, and device clouds.Appium
APIRequests, extraction, schemas, authentication, assertions, and attached payload evidence.REST Assured
DatabaseConnections, queries, updates, and result validation beside the product flow.JDBC
CLITerminal, container, SSH, and file actions with output preserved in the run.Local, Docker, SSH
Real product surfaces
Inspect the workflow, not a mockup.
These screenshots come from SHAFT’s report, browser capture, and IntelliJ tooling.
Architecture proof
Readable test intent. Shared lifecycle and evidence.
SHAFT owns repeatable mechanics while the underlying automation engines remain available.
@Testpublic void checkout_happy_path() { driver.element().click(addToCart) .and().click(checkout) .and().assertThat(orderStatus) .text().contains("Success");}SHAFT handles evidence attached
- driver lifecycle, waits, retries, and synchronization
- screenshots, logs, steps, and attachments
- configuration and data isolation
- Allure evidence that Doctor and Heal can inspect
Native engines stay visibleUse the underlying Selenium, Playwright, Appium, REST Assured, TestNG, JUnit, and Cucumber APIs when direct control matters.Review the technology mapDependencies stay alignedStart with the engine artifact for unified defaults, or use the SHAFT BOM to keep selected modules on matching versions.Review module choicesEvidence follows every surfaceKeep screenshots, logs, requests, responses, and diagnostics attached to the same run and reporting lifecycle.Review reporting
Adoption questions
Resolve risk before the pilot.
Use the implementation paths and primary-source project evidence to decide whether SHAFT fits your team.
Run where your team already builds
SHAFT projects use Maven and run from developer machines or CI. The framework keeps the same evidence model across those environments.
Review the first-run pathExtend without replacing native tools
Add only the modules your suite needs and keep direct access to the underlying automation libraries when a case calls for it.
Compare modulesEvaluate support and stewardship
Inspect the MIT terms, release history, security policy, CI results, and public support channels before adoption.
Review project evidenceDiagnostic loop
Turn a failed check into an explainable path.
Run the suite, collect the artifacts, diagnose the path, and improve the check using the same evidence trail.
01ExecuteRun web, mobile, API, database, and CLI checks from one Java project.
02CollectCapture screenshots, logs, requests, responses, and data facts.
03ReportPlace the timeline and attachments in an Allure evidence trail.
04DiagnoseUse the report and Doctor to understand the failure path.
05ImproveApply a deterministic fix, then use Heal when the evidence supports it.
Improve loops back to Execute. Every run repeats the cycle.
no account · no payment details · Maven project
Generate a free SHAFT project.
Choose the surfaces you need, download the project, and inspect the evidence from your first run.