ShaftHQ/SHAFT_ENGINE - Page 2

shaft-test-case-design

Use when designing reviewable test cases or scenarios with traceability, data, steps, expected results, techniques, priorities, and boundary coverage.

shaft-test-data-design

Use when designing deterministic, private, isolated SHAFT test data with partitions, factories, seeding, uniqueness, cleanup, retention, or schema rules.

shaft-test-environment

Use when defining or troubleshooting SHAFT test environment readiness, parity, versions, configuration, dependencies, isolation, reset, or drift.

shaft-test-execution

Use when executing approved SHAFT tests with controlled scope, preflight checks, deterministic configuration, evidence, status reconciliation, and cleanup.

shaft-test-monitoring

Use when monitoring SHAFT test progress, coverage, quality gates, defects, risks, duration, flakiness, infrastructure health, or completion.

shaft-test-planning

Use when creating or revising a risk-based SHAFT test plan covering objectives, scope, approach, resources, estimates, schedule, criteria, and monitoring.

shaft-test-recording

Use when an approved live web, Playwright, native-mobile, mobile-web, Appium Inspector, or API flow must be captured with privacy-safe evidence.

shaft-web-actions

Use when implementing SHAFT WebDriver or Playwright navigation, browser state, element interaction, upload, drag-and-drop, window, cookie, or screenshot behavior.