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.
The star prompt waits until evaluators have a successful first run to remember.

One framework. Full surface coverage.

Start with the layer in front of you, then expand without changing the reporting and lifecycle model.

SurfaceTestValidateDataStateObserveEvidence

Web GUITestValidateDataStateObserveEvidence Mobile GUITestValidateDataStateObserveEvidence APITestValidateDataStateObserveEvidence DatabaseTestValidateDataStateObserveEvidence CLITestValidateDataStateObserveEvidence

Boilerplate code removed from tests.

Clean tests that read like documentation. Let SHAFT own the repeatable mechanics that make evidence reliable.

SHAFT test

@Testpublic void checkout_happy_path() {  driver.element().click(addToCart)        .and().click(checkout)        .and().assertThat(orderStatus)        .text().contains("Success");}

SHAFT handles

SHAFT handles the repeatable work:
driver lifecycle, waits, retries, and sync
screenshots, logs, steps, and attachments
configuration and data isolation
Allure evidence that Doctor and Heal can read

Native engines stay nativeUse Selenium, Playwright, Appium, REST Assured, TestNG, JUnit, and Cucumber directly when control matters.Technology map Boilerplate code moves out of testsSynchronization, configuration, smart locators, screenshots, logs, and Allure steps live in the framework.Feature map Failures start with evidenceWeb, mobile, API, CLI, and DB actions attach evidence that Doctor and Heal can use for recovery.Reporting guide

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 guide