13 docs tagged with "best-practices"

SHAFT runtime, module, facade, and agent integration architecture — plus where SHAFT fits in a general test automation stack and the engine-vs-framework distinction.

Use Allure annotations to generate business-readable BDD-style reports without Cucumber — simpler setup, better maintainability.

Use SHAFT Engine's 500+ pre-built Gherkin step definitions for browser, element, and assertion steps — integrate Cucumber without writing boilerplate glue code.

When to combine Android and iOS tests in one project vs. separate projects, and how to handle platform-specific locators with SHAFT Engine.

Locate web elements using ID, CSS selectors, XPath, SHAFT Locator Builder, relative locators, shadow DOM, iframes, By objects vs @FindBy, dynamic locators, and cross-platform Android/iOS locators.

Learn how to use SHAFT Engine's fluent API to chain actions and validations for readable, maintainable test code.

How to run SHAFT Engine tests in CI/CD pipelines — configuring properties, headless execution, and pipeline integration tips.

Split a SHAFT suite across parallel shards with -Dshaft.shard=N/M, then merge every shard's Allure results into one report and speedboard.

Where to find SHAFT Engine test artifacts — Allure reports, execution summaries, and how to publish them from CI/CD pipelines.

Compare test automation design patterns — Page Object Model, fluent design, anonymous classes, inheritance, and base classes — with SHAFT Engine examples.

Key criteria for selecting a test automation tool or framework, and how SHAFT Engine addresses each one.

Understand the difference between isolated test cases and dependent test scenarios, and why you should avoid using priority to order tests.

Understand the testing pyramid, the role of each testing level, and how to build an effective test automation strategy with SHAFT Engine.