A scenario is versioned YAML — an objective, a role, assertions and budgets. No selectors, no coordinates, nothing to rewrite when the interface changes.
A scripted test encodes how the interface looked on the day it was written, which is why a redesign breaks tests whose business process still works perfectly. An Argus scenario states the objective, the role and what must be true at the end, and lets the agent work out the clicks — so the test survives changes that would have broken a script.
A scenario is an objective, a role, assertions and budgets.
No selectors and no coordinates to maintain.
A redesign does not invalidate the test.
Scenarios are versioned YAML, reviewable like code.
App-specific quirks live in one shared notes file, not per scenario.
Nothing needs to. The agent perceives the live screen and works out the interaction itself.
Never in the scenario. A role name resolves through an encrypted secret store, and login is scripted deterministically.
Each one carries step and time budgets, alongside loop and stall detection.
Creator, approver and supplier each get a fresh, independently authenticated session.
A lost agent is never filed as a product defect.
A passing run distils its path into intents, never coordinates, for later runs to reuse.
Every model call is metered and aggregated from call to suite.
See the complete product: problem, features, how it works and deployment.
Request a demo to watch a multi-role regression suite run through your real interface.