Write the test. SHAFT does the rest.

One Java engine for web, mobile, API, CLI, database, and desktop.
Drivers, waits, and evidence are handled. Every run ends in an Allure report.

Why SHAFT

• No plumbing. Managed Selenium and Appium drivers, synchronized actions, and smart waits.
• One fluent API. Web, mobile, REST/GraphQL, database, CLI, and desktop in the same test.
• Evidence by default. Steps, screenshots, and logs land in an Allure report on every run.
• Scale by configuration. Local, Grid, BrowserStack, or LambdaTest; TestNG, JUnit, or Cucumber.
• Open and trusted. MIT licensed, on Maven Central, with public coverage.

How it works

Test intent and configuration enter SHAFT’s orchestration layer, fan out across the execution surfaces you need, and come back as unified evidence.

flowchart LR
    accTitle: SHAFT execution and evidence workflow
    accDescr: Test intent and configuration enter SHAFT orchestration, run across Web, Mobile, API, and Native execution surfaces, and produce unified evidence.
    I[Test intent] --> S[SHAFT orchestration]
    C[Configuration] --> S
    S --> W[Web]
    S --> M[Mobile]
    S -->…