ShaftHQ | SHAFT User Guide

Maximize ROI & Efficiency

Focus on designing your tests while SHAFT handles synchronization, screenshots, logging, and reporting with zero boilerplate code

All-in-One Solution

Unified engine for Web, Mobile, API, CLI, and Database test automation—no more juggling multiple tools

Wizard-Like Syntax

Intuitive fluent API: just type SHAFT. and discover all capabilities instantly

Award-Winning Framework

Google Open Source Peer Bonus award winner and trusted globally

Official Selenium Ecosystem

Proud member of the official Selenium ecosystem frameworks with 40,000+ active users worldwide

Future-Proof & Standards-Compliant

W3C standard compliant, WebDriver BiDi enabled, and fully supported by the Selenium project

What's your Return on Investment?
ROI = (^Savings/_Investment) * 100

# Tests to be automated:		Exhaustive automation is not possible, so as a maximum try not to exceed `80%` of your total tests.
Average manual execution time (minutes/test):
Estimated # test runs per year:		• If you plan to execute your tests as Nightly Builds, then input `365`. • If you plan to execute only once every sprint. then input `# sprints per release * # releases per year`.
# Target test execution platforms:		• If you plan to execute your tests against 3 browsers (CH,FF,SA) and 3 operating systems (Win/Lin/Mac) then input `9`. • If you plan to use SHAFT for Mobile GUI testing, then input a minimum of `2` for Android and iOS. Feel free to multiply by the number of OS versions and device manufacturers if you want to target more devices. • If you plan to use SHAFT for API/CLI/DB testing, then input `1`.

📱 Calculate ROI 📱

Assumptions:
• Automated execution effort = 5% from the manual execution effort (if not 100% unattended).
• Upskilling effort = 1 work week.
• Framework dev effort = 1 work day.
• Maintenance effort = 0.5 hours per test run.
• Sequential execution (Multiply the above ROI * Number of parallel threads).