See BuniOD in action
A short walkthrough: connect an application, describe a flow, review the generated scenario and run it in a real browser.
Five steps. Two of them are yours.
You describe the flow and confirm the scenario. BuniOD generates it, runs it and records the results.
Connect your application
Add your application’s URL. Public pages work from the URL alone. Signed-in flows need a dedicated test account — HTTP basic auth or a test identity.
Describe what to test
Write the task and the result you expect in plain language. No syntax, no test-case template, no scripting.
Get a scenario
BuniOD works through your application in a browser and records the steps, the test data and the checks for the expected result.
Review and refine
Read it back. Adjust an input value, or update the prompt and regenerate. Nothing runs until you confirm it.
Run and review results
Run confirmed scenarios manually or on a daily schedule. Moved elements are re-matched where supported, and each result is stored with screenshots and logs.
The entire flow, visualized
From the sentence you type to a stored result your team can inspect.
Your Application
You add a URL and, if needed, test access.
Your Prompt
You describe the task and the expected result.
Guided Browsing
BuniOD opens your application and works through the task.
Scenario Generation
Steps, test data and checks are recorded.
Review & Confirmation
You confirm the scenario before it runs.
Execution
The scenario runs in a real Chromium browser.
Element Matching
Moved elements are re-matched where supported.
Results
Step results, screenshots and logs are saved.
Notifications
Email and in-app alerts reach your team.
How BuniOD turns a description into a scenario
Your prompt carries the intent. BuniOD combines it with what it sees in your application to produce steps that run.
Public pages or signed-in flows. You choose.
Start with nothing but a URL. Add test access when the flows you care about sit behind a login.
URL only
Point BuniOD at your product, describe a public flow and review the scenario it generates.
- No source code required
- Nothing to install
- Runs in a real Chromium browser
- Manual and daily scheduled runs
Test access
Authenticated flows require a dedicated test account. Add it once and reuse it across scenarios.
- HTTP basic auth, encrypted at rest
- Test identities with their own inbox
- Checks for emails your app sends
- Best used on non-production environments
What happens when a scenario runs
Whether you start it yourself or the daily schedule does, every run follows the same cycle.
Run starts
You click run, or the daily schedule starts it.
Browser opens
A fresh Chromium session opens your application.
Steps replay
Confirmed steps run in order, with their test data.
Elements re-matched
If an element moved, BuniOD tries to locate it again.
Checks evaluated
Expected results are verified: text, URLs, requests, emails and more.
Results saved
Step results, screenshots and logs go into run history.
Team notified
Email and in-app notifications, based on each person’s settings.
What BuniOD produces
Scenarios you can read and results you can inspect.
Scenario Library
Every scenario you generated, with its steps, test data and checks.
Business Processes
Scenarios grouped into ordered runs, with dependencies between them.
Run History
Every run with its status and results.
Screenshots & Logs
Screenshots, console output and network activity for each run.
Failure Explanations
The step or check that failed, and why.
Agent Questions
Questions BuniOD raises when it cannot tell what to do.
Token Usage
How many tokens your work used this period, against your plan.
One platform, every role
Different people get different value from the same scenarios.
Visibility without extra tooling
- A pass/fail record for every run
- Daily checks of key flows
- Token-based pricing, no per-seat fees
Stop writing scripts
- Scenarios generated from descriptions
- Fewer locator fixes after UI changes
- More time for edge cases and exploratory work
See where it broke
- Failed step and explanation
- Screenshot at the point of failure
- Console and network logs
Keep key flows checked
- Daily scheduled runs
- Business processes that run in order
- Team access per project
Write the flow, read the result
- Acceptance criteria in plain language
- Steps you can read without code
- Severity labels on scenarios
Test staging safely
- Point projects at staging URLs
- HTTP basic auth support
- Dedicated test identities
Security, stated precisely
What BuniOD accesses, what it stores and what to know before you run it.
No source code required
BuniOD tests your application through the browser. It doesn’t need access to your repository.
Encrypted credentials
HTTP basic-auth credentials are encrypted at rest with AES-256-GCM.
Project isolation
Each project is visible only to the members you invite.
Tests act as a user
Scenarios interact with your application and may create or update test data. Use test accounts and non-production environments where possible.
AI processing
Prompts and the structure of tested pages are processed by Google and OpenAI models.
Questions, answered
Generation starts as soon as you submit a prompt. BuniOD works through your application in a browser, so the time depends on the length of the flow and how quickly your pages respond.
No. BuniOD works from your application’s URL. It does not connect to code repositories.
Yes. Add HTTP basic auth or a test identity. Authenticated flows require a dedicated test account.
Whenever you start a run, and once a day on the schedule you set. You choose the time and can switch the schedule off.
Adjust an input value, or update the prompt and regenerate. Nothing runs until you confirm the scenario.
Ready to generate your first scenario?
Create a free account, add your application and describe the first flow you want to verify.
Start free