io.github.shafthq : shaft-engine
Ship automation evidence, not boilerplate code.
One Java test suite for web, mobile, API, DB, and CLI. SHAFT keeps your native tools in view while moving sync, evidence, and recovery into the framework.
Built for engineers. Read by leaders.
For engineers
Keep native Java control while SHAFT standardizes the repeatable suite work.
- Selenium, Playwright, Appium, REST Assured, JDBC, and CLI stay visible.
- Waits, retries, reporting, screenshots, and logs move out of test code.
- Evidence is readable when the next failure interrupts real delivery work.
For leaders
Turn automation from a hidden maintenance cost into release evidence people can inspect.
- One guide path helps new projects, migrations, and cross-surface expansion.
- Failures start with artifacts that explain what changed and where to look.
- Allure reports give leaders an inspectable evidence trail for every release run, not just a pass/fail badge.
Get started in minutes.
Install, configure, write a readable test, run it headlessly, and review the evidence before starring the repository.
Add the dependency
<dependency>
<groupId>io.github.shafthq</groupId>
<artifactId>shaft-engine</artifactId>
<version>10.3.20260722</version>
</dependency>
One framework. Five testing surfaces.
Start with the layer in front of you, then expand without changing the reporting and lifecycle model.
Boilerplate code removed from tests.
Clean tests that read like documentation. Let SHAFT own the repeatable mechanics that make evidence reliable.
@Testpublic void checkout_happy_path() { driver.element().click(addToCart) .and().click(checkout) .and().assertThat(orderStatus) .text().contains("Success");}- driver lifecycle, waits, retries, and sync
- screenshots, logs, steps, and attachments
- configuration and data isolation
- Allure evidence that Doctor and Heal can read
Allure evidence people can inspect.
SHAFT turns each checkout action into report evidence: steps, screenshots, logs, and diagnostics stay attached to the run instead of scattered across CI output.
Open reporting configuration reference
The evidence loop makes failures explainable.
Run the suite, collect the artifacts, diagnose the path, and improve the checks with the same evidence trail.
Improve loops back to Execute — every run repeats the cycle.
run complete · evidence attached · exit 0
Generate your first SHAFT project.
Run the CLI, produce evidence, and see what your team gets. Questions first? Join the Slack community.