Workflows around
your test runs.
If/else, foreach, parallel branches, wait-for-event, and per-step error handlers — the control flow you want in production code, applied to your tests.
How It Works
The run pipeline
Every Viziera run flows through the same seven stages — wrap them in branches, loops, and approval gates as your release pipeline grows.
Trigger
PR webhook, schedule, or manual run
Plan
Scenarios + viewports selected
Auth
Keychain creds + 2FA hand-off
Drive
Browser or native execution
Approve
Optional human gate
Observe
Screens, network, AI signals
Report
PR status + Slack + findings
Tests on every PR. Not on a flaky schedule.
A bearer-token webhook fires Viziera on every pull request. Scenarios run, results post back as a status check, and the merge is blocked if anything regresses. No bespoke YAML required.
Parallel branches. Conditional merges.
Run desktop, mobile, and tablet scenarios in parallel. Branch on environment, feature flag, or PR metadata. The workflow engine treats steps as first-class — same primitives you'd use in real code.
Pause for a human. Resume on a click.
Wait-for-event steps pause the run until a teammate approves in the Viziera app, in Slack, or in a PR comment. Use for visual baseline updates, accessibility regressions, or anything compliance-touched.
Nightly. Hourly. Whenever you want.
Schedule the long-tail scenarios that don't belong on every PR — nightly accessibility sweeps, weekly visual regression baselines, monthly load runs.
AI proposes findings. You decide what to fix.
The autonomous beta tester files findings; you decide which become tickets, which update the baseline, and which get dismissed. Every decision feeds back into prioritization.
Build a releasepipeline you trust
Compose tests, approvals, and post-run actions into a workflow that fires on every PR and shows up where your team already works.