SHAFT

Reliable Java test automation, from first intent to production-grade evidence.

One strong, maintainable framework for Web, Mobile, API, CLI, Database, and native testing—with synchronized actions, configuration-first execution, readable assertions, and unified reports.

Generate your first project · Explore the user guide · Star SHAFT on GitHub ⭐

SHAFT removes the repeated plumbing around drivers, waits, assertions, configuration, test data, screenshots, logs, and Allure evidence. Its modular Maven reactor keeps the core lean and lets teams add advanced tooling only when they need it.

From zero to useful evidence

1. Open the SHAFT landing page and generate a ready-to-run Maven project.

2. Extract it and run:

   mvn test
   

3. Inspect the sample result, screenshots, logs, and Allure evidence.

The generated project uses the canonical Maven coordinate io.github.shafthq:shaft-engine and gives you a repeatable baseline for local runs and CI.

One orchestration layer, every execution surface

Test intent and configuration enter SHAFT's orchestration layer, fan out across the required execution surfaces, and return through one unified evidence flow.

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 --> A[API]
    S --> N[Native, CLI, and Database]
    W --> E[Unified evidence]
    M --> E
    A --> E
    N --> E

Built for long-lived automation suites

• Strong defaults, explicit control. Sensible behavior gets teams moving; configuration keeps environments and CI reproducible.
• Modular by design. Start with shaft-engine, then adopt visual, video, cloud, native, or agentic modules without rebuilding the test architecture.
• Evidence is part of execution. Logs, screenshots, attachments, and reports share one lifecyc

... View full README on GitHub