What's new since modularization
Find user-facing capabilities added since 10.2.20260610 (2026-06-10). Search
by feature name or filter by the job you need to complete. Each result opens a
focused page with setup, usage, and canonical guide links.
Capability atlas
Find the feature for your goal
61 features
Platform and setup
Install, upgrade, and connect the infrastructure your tests need.
- Modular artifacts and BOMSplit SHAFT into a core engine and optional artifacts while one BOM aligns their versions.Configure and use
- Automated upgrade toolMigrates supported older SHAFT, Selenium, Appium, and REST Assured projects to modular coordinates and current APIs.Configure and use
- Project GeneratorCreates a ready-to-run Maven project from selected runner and test surfaces.Configure and use
- Properties GeneratorBuilds a focused SHAFT properties file from the supported configuration catalog.Configure and use
- Managed local AI runtimeInstalls supported local agent tooling and required runtimes through the project installer.Configure and use
- Android and Appium setupPrepares Android SDK, emulator, Appium, and driver prerequisites for SHAFT mobile tests.Configure and use
- iOS and Windows Appium setupDocuments the platform-specific drivers and hosts required for iOS and Windows application sessions.Configure and use
- Selenium Grid preflightChecks remote Grid connectivity and browser availability before execution.Configure and use
- Healenium setupConnects SHAFT web execution to a Healenium service when that integration is selected.Configure and use
- ReportPortal setupConnects test execution to a configured ReportPortal instance.Configure and use
- BrowserStack LocalCreates a secure tunnel between BrowserStack sessions and sites reachable from the test machine.Configure and use
- Playwright browser installationInstalls the browser binaries required by SHAFT's Playwright backend.Configure and use
- Lighthouse setupPrepares the browser tooling used by SHAFT performance audits.Configure and use
Capture and generation
Record working journeys and turn them into reviewable test code.
- Browser recording and codegenRecords browser interactions and generates maintainable SHAFT steps.Configure and use
- Browser API recordingCaptures browser network calls and produces API-oriented replay blocks.Configure and use
- Native mobile API captureRecords API traffic associated with an active native mobile session.Configure and use
- Recorder assertions and step editingAdds assertion mode, locator picking, record-at-target, and step editing to the recorder workbench.Configure and use
- Scenario-to-code generationConverts a reviewed Capture scenario into SHAFT test code.Configure and use
- Verified test-ID replayPrefers unique author-written test IDs and verifies generated steps through replay.Configure and use
Agentic tools
Use deterministic local tools, IDE workflows, and optional providers.
- SHAFT PilotProvides provider-neutral contracts and local orchestration through shaft-pilot-core.Configure and use
- IntelliJ AssistantProvides project-scoped guidance and SHAFT tools inside the IntelliJ plugin.Configure and use
- IntelliJ test run, debug, and watchRuns, debugs, and watches focused SHAFT tests from the IDE tool window.Configure and use
- SHAFT DoctorAnalyzes allowlisted Allure evidence and failure traces locally.Configure and use
- SHAFT HealProposes deterministic, explainable recovery for eligible changed web locators.Configure and use
- MCP, CLI, and agent skillsExposes the same local SHAFT capabilities through MCP clients, one-shot CLI calls, and task-specific skills.Configure and use
- ChaosEngine harnessInstalls a project-local agent workflow with verified host adapters and local tooling.Configure and use
- Optional AI providersAdds provider advice through opt-in adapters that remain disabled by default.Configure and use
- Planning test coverageCrawls same-origin content deterministically and drafts a Markdown test plan in specs/.Configure and use
- Trust-gated natural-language actionsTranslates approved intent into GUI actions through a separate surface that is disabled by default.Configure and use
Evidence and reports
Understand failures from portable reports and structured artifacts.
- Evidence level profilesControls how much SHAFT evidence each run retains through named profiles.Configure and use
- Failure Trace ViewerAttaches a self-contained failed-test timeline with available DOM, network, console, and locator evidence.Configure and use
- Failure diagnostics bundlePackages sanitized metadata, bounded logs, and referenced artifacts into shaft-diagnostics.zip.Configure and use
- Failure brief and attachment manifestAdds a concise HTML failure brief and a JSON inventory of attached evidence.Configure and use
- Validation, accessibility, visual, and API evidenceAttaches structured evidence for supported assertions, accessibility checks, visual comparisons, and API validations.Configure and use
- Soft verification and checkpoint JSONRecords verification checkpoints in structured JSON while allowing the test to continue to its final verdict.Configure and use
- Sharded report mergeCombines result artifacts from parallel CI shards into one report input.Configure and use
- Backend-neutral offline trace expansionExpands supported Selenium and Playwright action evidence into the same offline trace surface.Configure and use
- Locator health reportsRecords locator score and stability information for locators used during a run.Configure and use
- Flake and auto-wait profilerRecords flake risk and auto-wait behavior for investigation.Configure and use
- Allure SHAFT overview panelAdds SHAFT run and evidence context to the generated Allure overview.Configure and use
- Native Playwright tracesRetains supported Playwright trace ZIPs beside SHAFT evidence.Configure and use
Testing APIs
Exercise web, mobile, API, contract, visual, and accessibility behavior.
- Playwright GUI backendRuns SHAFT GUI actions through Microsoft Playwright.Configure and use
- GraphQL API actionsSends GraphQL operations through SHAFT API actions.Configure and use
- Typed API responses and retry policiesMaps supported API responses to Java types and applies explicit retry policies.Configure and use
- OpenAPI coverageCompares exercised API operations with an OpenAPI description.Configure and use
- Network interceptionObserves, modifies, or stubs supported browser network traffic.Configure and use
- Authentication state and HAR replayReuses browser authentication storage and recorded HAR traffic in supported Playwright sessions.Configure and use
- UI and API contract replayRecords and checks UI and API interactions against reviewable contracts.Configure and use
- Cross-backend browser and mobile namespacesOrganizes supported Selenium, Playwright, and mobile actions under explicit SHAFT namespaces.Configure and use
- Focused validationsProvides scoped browser, element, object, number, file, and API assertion builders.Configure and use
- ARIA snapshots and visual baselinesChecks accessible structure and rendered appearance against reviewed baselines.Configure and use
- Flutter mobile APIAdds Flutter-aware actions for supported Appium sessions.Configure and use
- Android performance evidenceCollects supported Android performance measurements with the test evidence.Configure and use
- Image targets and OCR scroll previewUses published image targets, while recognized-text targets remain an unreleased shaft-ocr preview.Configure and use
- Remote terminal, SFTP, SSH, and port forwardingRuns supported remote file and shell operations, including SSH port forwarding.Configure and use
Integrations and modules
Add focused capabilities without expanding every project.
- BrowserStack, video, visual, and SikuliX artifactsPackages cloud execution, recording, image comparison, and desktop image automation as focused artifacts.Configure and use
- OCR and PDF OCR previewPreviews visible-text recognition for images and PDFs; shaft-ocr is not in the current published release or BOM.Configure and use
Features you might have missed
Find useful validation and locator features added around the modular release.
- Smart LocatorsFinds likely input and clickable controls when a stable locator is not yet known.Configure and use
- ARIA role locatorsBuilds locators from an accessible role and normalized visible text.Configure and use
- Localization assertionsValidates text language and direction through ValidationEnums.TextLanguage and TextDirection.Configure and use
- Allure 3 compatibility modeGenerates managed Allure 3 reports while retaining explicit compatibility behavior for Allure 2.Configure and use
Use the search field directly. No setup is required:
GraphQL