Testing that proves itself
Describe a test in plain English. An executor drives the real trading UI, a separate judge cites the pixels, and you get video, a trace, and a verdict you can forward.
Testing isn't about clicking.
It's about evidence.
Ryvetz turns a written flow into an executed test, has a separate judge cite the screen, and runs it on hosted runners we operate.
No selectors. No agent in your product. No real money.
It starts with a sentence
Write the test the way you would say it to a colleague. The agent grounds every step on the live screen at run time, so nothing depends on selectors or coordinates.
Explore Flowsname: Place a bracket order and flatten app: topstepx account: practice steps: - do: Open the order ticket for MNQ - do: Set quantity 2, bracket with a 10-tick stop - do: Submit and wait for the fill verify: The positions table shows 2 MNQ within 15 seconds - do: Flatten the position verify: No open position within 15 seconds
Plain-English steps
What to do, and what must be true afterwards. No page objects, no locators.
Learn moreGrounded on pixels
The executor finds the control on the real screen, the way a human would.
Learn moreRecovers from drift
A changed screen is seen and handled, not a missing selector that breaks the run.
Learn moreA verdict that cites pixels
The agent that clicks never grades itself. A separate strict judge sees only your criterion and the screenshot, and quotes what it used before anything passes.
Explore the Judge- The live screen
- The step to perform
- The Atlas of known controls
- Your verification criterion
- The screenshot. Nothing else.
“A failed image load in Support › Mini Tutorials: the URL reads ‘…topstep.comundefined/’, missing the path separator.”
Split roles
Executor and judge are different models with different instructions. One acts, one decides.
Learn moreCriterion and screen only
The judge never sees the executor’s reasoning, so it cannot be talked into a pass.
Learn moreStrict by default
A pass the judge is not confident in is recorded as a fail, with the evidence attached.
Learn more“Yes, one broken element was found: a failed image load in Support > Topstep's Mini Tutorials with malformed URL 'https://strapi-cms.topstep.comundefined/' missing a path separator between domain and path component.”
How the judge works
Evidence your pipeline can gate on
Video, screenshots, and a typed trace for every run, plus JSON and exit codes. On Team, every pull request gets a check run that fails when the judge does.
Explore EvidenceCI check runs
Install the GitHub App or call the webhook. Fail the release when the judge does.
Learn moreShare links
Time-limited URLs so a release manager can read the verdict without an account.
Learn moreBuilt for the release ritual, not the live desk
Trading software still ships on manual clicking before every release. Ryvetz replaces that ritual on practice accounts, with guards that live in the engine.
- Practice and demo only
Flows declare the account class up front. The shared runner refuses eval, funded, and live accounts.
- A session guard in the engine
A click that would sign out, or a screen that suggests real funds, is refused before it happens. Not a prompt rule: a seam.
- Dedicated for real money
Real-money account classes live on single-tenant runners under Enterprise, never on a shared slot.
Ship the terminal with evidence.
Every workspace starts at $0 with $30 of free credits. Describe one flow, watch it run on a hosted machine, and read the verdict.