automation-aura

Cucumber/TypeScript functional automation suite built on the shared @sai/applied-ai-aura framework, covering public frontend flows (home, about, contact, services, privacy, terms, login, preview health) with structured JSON reporting.

Technical foundation

Local package automation/ (@sai/delivery-automation) depends on the shared framework at shared/automation/applied-ai-aura.
Cucumber config automation/cucumber.js: feature glob src/features/**/*.feature, shared world/hooks (AuraWorld.ts, hooks/index.ts), shared common/preview steps plus local src/steps/**/*.ts.
Reporters: progress formatter plus json:reports/cucumber-report.json; run mode parallel: 1.
Test orchestrators in automation/src/tests/: AuraSuiteTest.ts (full suite, supports --tags @smoke/@regression), plus scenario-focused runners such as HomeTest.ts and LoginTest.ts.

Feature and step coverage

Feature file	Step definitions	What it covers
`Home.feature`	`Home.steps.ts`	Landing page navigation, hero content, and primary CTAs.
`Login.feature`	`Login.steps.ts`	Admin login form validation and authentication happy path.
`Privacy.feature`	`Privacy.steps.ts`	Privacy policy page rendering and navigation links.
`About.feature`	Shared common/preview steps	About page content and section navigation.
`Contact.feature`	Shared common/preview steps	Contact form submission flow.
`Services.feature`	Shared common/preview steps	Service catalog listing and detail navigation.
`Terms.feature`	Shared common/preview steps	Terms and conditions page rendering.
`PreviewHealth.feature`	Shared common/preview steps	Preview environment health/smoke check before full suite execution.

Reuse patterns and acceleration factors

Shared world/hooks and step libraries in applied-ai-aura remove the need to re-implement browser bootstrap, screenshot capture, or reporting per project.
Tag-based execution (@smoke, @regression) allows targeted runs in CI without duplicating suite definitions.
Local constants files (HomeConstants.ts, LoginConstants.ts) centralize selectors/text so page markup changes require a single-file update.

Example acceptance criteria for this module

Given a new public page is added, a corresponding .feature file exists under src/features/ with at least one happy-path scenario.
Given the suite runs in CI, the JSON report is written to reports/cucumber-report.json and uploaded as a build artifact.
Given the login flow changes, Login.feature and Login.steps.ts are updated in the same pull request.