How it works
Test authors write human-readable scenarios to script behavior without writing the underlying code. Engineers write code for application-specific needs without reinventing the plumbing. PrideForge handles the rest.
Working automation foundation
Open-source stack integrated into a cohesive framework your team runs and extends. Scenarios stay stable while the framework and page objects absorb UI and environment change.
From Gherkin to browser
Scenarios are easy to read for non-technical reviewers: each one says what was done and what was validated. Readable Gherkin is wired to shared steps and page objects so the same language drives the automation.
Handler priority
Handlers resolve controls from most specific to least specific — vendor widgets and compounds before HTML primitives, with a generic catch-all last. Add your own in the customization layer and register early to override a built-in, or pick a band that matches how specific your control is.
Targeted runs with tags
Tag features and scenarios with @env, @smoke, or your own labels —
then filter what executes locally or in CI without rewriting scenarios.
