burhānnoun, Arabic· Proof; clear evidence that settles the question.
The little QA dog that finds your bugs first.
Burhan is an AI QA tester for your web app. Give him your staging link: he runs through every screen, writes your docs if you have none, turns them into test journeys, and barks at every bug with a video and a report your developers can paste. No test code, no scripts.
Free Starter plan: one module, no card, no time limit.
- SGN-01New user signs up with a work emailpassed
- TEAM-03Admin invites a teammatepassed
- INV-07Send an invoice with a 10% discountfailed
- ACC-02Reset password from the email linkpassed
Step 4 · Tap Send · Actual: total stays at $1,000.00
- 09:41:02Ears up: reading Invoices PRD v3, section 4
- 09:41:066 journeys drafted for the Invoices module
- 09:41:11Signed in as Primary account · staging
- 09:41:15INV-07 · step 3 · Add a 10% discount
- 09:41:16INV-07 · step 4 · Tap Send
- 09:41:16POST /api/invoices/send → 500
- 09:41:17WOOF! Fetched the video, steps, API call and console error
- 09:41:17Bug report ready for Backend
Tiny dog. Huge bark. Zero chill about bugs.
A Chihuahua with radar ears and endless energy. Here's his day at work:
Ears up
He reads your docs, or explores your app when you have none.
Paws flying
He runs every journey in a real browser on your staging site.
WOOF!
He barks the moment something breaks, with the video to prove it.
Tail wagging
All green? You'll see it on his face. Ship it.
Shipping fast shouldn't mean your customers find the bugs first.
Manual QA can't keep up with weekly releases.
Before every release
- Someone clicks through the same flows by hand
- Test scripts break every time the UI changes
- Bug tickets that just say “it doesn't work”
With Burhan
- ✓Journeys written from your own spec, or from docs he writes for you
- ✓Reread when the spec changes, no scripts to fix
- ✓Every failure comes with steps, a video and the API error
Two questions in, he already knows your app.
Type your staging link and tell him how to sign in. By the time you reach the next step, Burhan has had a look around and comes back with what he dug up: what your app does, its main areas, and the docs that would help most.
01 · Where does your app live?
staging.acme.app
02 · How does he sign in?
qa@acme.app · ••••••••
- Continue… and a minute of magic
Guess what I dug up?
I did my magic while you weren't looking. Ta-da!
Fetched for you · Invoicing app
- ✓ I'm in!
- ✓ Got past the sign-in
- ✓ 7 areas dug up
An invoicing app for small agencies: clients, invoices with discounts, payments and team roles.
- Dashboard
- Clients
- Invoices
- Payments
- Team
- Reports
- Settings
No docs? He'll write them.
Most teams don't have a perfect spec. Burhan explores your app the way a new teammate would, without changing a thing, and writes your product documentation. Then he tests against it.
- 01Explores every screen, signed in with your test account
- 02Never saves, deletes, pays or sends anything
- 03Growth and Pro go deeper: more screens, plus what's public about you on the web (your site, help center, LinkedIn, app stores)
- 04The doc is yours: edit it, download it for Word, share it with your team
Acme: product documentation
Written by Burhan · 8,552 characters
Invoices
Create an invoice for a client, add line items and a discount, then send it by email.
Clients
A list of clients with their contacts, open invoices and total paid.
Team
Invite teammates as Admin or Member. Members can't see Settings.
Got a recording instead? Drop in a demo video or a meeting recording and he turns it into notes.
From your staging link to a bug report, without writing code
staging.yourapp.com
+ docs, if you have them
01Point him at your app
Your staging link and a test account. Add docs if you have them: PDFs, GitHub, links, even recordings. No docs is fine too.
6 journeys
Drafted from section 4
02He writes the journeys
Module by module, he turns your docs into user journeys: what a real user does and what should happen. Your team checks them before anything runs.
Running · step 3/6
Real browser · staging
03He runs them
Each journey runs in a real browser on your test accounts, clicking through just like a user would.
Bug report
Ready to paste
failed · INV-0704He barks at bugs
A video, the failing step, API calls and console errors, and a bug report your developers can act on straight away.
Feed him anythingPDFMarkdownGoogle DocsGitHubLinksAudio & videoNo docs at all
Every failure comes with a bug report that's ready to paste
No more “it doesn't work” tickets. Burhan says what it did, what your spec expected, and what happened instead.
INV-07 · Send an invoice with a 10% discount
Failed at step 4 of 6 · staging · Primary account
Steps
- Sign in as the admin of a test company
- Create an invoice for $1,000.00
- Add a 10% discount
- Tap Send
Expected
The total shows $900.00 and the invoice is sent to the client.
from “Invoices PRD v3, section 4.1”
Actual
The total stays at $1,000.00 and nothing is sent.
Likely owner Backend
▶ Video · 0:42- 01What it did, step by step
- 02What your spec says should happen
- 03The API call and console error behind it
- 04Who should probably fix it
AI test automation for product and QA teams that ship every week
- No-code test automation
- Nothing to write or maintain. When the spec changes, Burhan rereads it.
- Writes your docs
- No spec? He explores your app and writes one for you to edit, download and share.
- Checks against your spec
- He tests what your docs say should happen, not what he guesses.
- Feed him anything
- PDFs, Markdown, GitHub, links, even demo videos and meeting recordings.
- One test account is enough
- Missing the data a test needs? Burhan mocks only that data and labels the run. Real data first, always.
- English and Arabic
- Docs and apps in either language, right-to-left layouts included.
- Staging first
- Test staging before every release, and keep production separate.
- Passwords stay private
- Test-account passwords are never shown to the AI.
- Faster regression testing
- Fixed something? Re-run only the failed journeys without testing everything again.
- Release health at a glance
- See which modules pass, fail or are blocked, release after release.
Simple pricing, per project
Start free with one module. Upgrade a project when you want every module tested.
Try Burhan on one module
$0/ project / month
- One module of your choice
- Its journeys run once a week
- Docs written from a quick tour
- One retry when a run fails
- Video, API calls and bug reports
- One-click tickets in Jira and ClickUp
- No card, no time limit
Test the whole product every week
$99/ project / month
- Every module in your docs
- Your in-app AI assistant, tested too
- A full test every week
- Docs from a deep tour plus web research
- Re-run failed journeys up to 50 times a week
- Extra full runs at $25
- Video, API calls and bug reports
- One-click tickets in Jira and ClickUp
Test the whole product every day
$249/ project / month
- Every module in your docs
- Your in-app AI assistant, tested too
- A full test every day
- Docs from a deep tour plus web research
- Re-run failed journeys up to 200 times a week
- Extra full runs at $12
- Video, API calls and bug reports
- One-click tickets in Jira and ClickUp
Questions teams ask us
Q.01What is AI QA testing?
AI QA testing means an AI does the work of a manual tester: it reads what your product should do, clicks through your web app in a real browser, and reports what broke. Burhan does this from your own product docs, so every test checks your spec.
Q.02Do I need to write any tests?
No. Burhan writes the user journeys from your docs. Your team reviews them, and you can edit, add or remove any journey.
Q.03How is Burhan different from Selenium, Cypress or Playwright?
Those are test automation frameworks: an engineer writes test scripts and keeps fixing them when the UI changes. Burhan is an AI QA tool: it writes the end-to-end tests from your docs and runs them for you, so there are no scripts to maintain.
Q.04We don't have docs. Can we still use Burhan?
Yes. Burhan explores your app with your test account, without changing anything, and writes your product documentation. You can edit it, download it for Word and share it, and he tests against it.
Q.05What kind of docs work?
PRDs, user stories, specs and acceptance criteria: PDF, Markdown or text files, Google Docs or Drive links, files in a GitHub repo, or audio and video recordings, which he turns into notes.
Q.06Can it test pages behind a login?
Yes. You add test accounts for your staging site and Burhan signs in with them. The passwords are never shown to the AI.
Q.07Our test account doesn't have all the data. What then?
One test account is enough. When a journey needs data the account doesn't have, Burhan mocks it for you: he takes the real API answer, changes only the fields the test needs, and checks the screen. The result is labelled “mocked”, pass or fail, and says what was changed. Every run tries the real data first, so once your account has it, the label goes away. He never mocks sign-in or anything that saves, and you can turn mocking off in Settings.
Q.08Can Burhan open tickets in Jira or ClickUp?
Yes, on every plan. Connect Jira or ClickUp once, pick the project or list, and every red run gets a Create ticket button: the steps, expected vs actual, which side owns it, the API calls and the screenshot go straight into the ticket. When the journey passes again, Burhan says so on the ticket. You can still copy the bug report instead.
Q.09Does it test production?
Burhan is built for staging, so bugs are caught before release. You can add production as a separate environment.
Q.10Can Burhan test the AI assistant in our app?
Yes, on Growth and Pro. Burhan asks your in-app chatbot real questions, opens the screen that should agree, and flags every answer that doesn't. It also checks it refuses tricks, never acts without a yes, and gives the same answer in English and Arabic.
Q.11Does it work with Arabic apps?
Yes. Docs and apps can be in English or Arabic, right-to-left layouts included.
Q.12What does the free plan include?
Starter covers one module of your choice per project. Its journeys run once a week, with one retry when a run fails. No card, no time limit.
Q.13Can I cancel any time?
Yes. Plans are monthly and per project. Cancel from Billing and the plan stays until the end of the month you paid for.
Q.14Why a dog?
Because a good QA tester is like a good dog: curious, tireless, loyal to your users, and loud when something's wrong. And Burhan means proof in Arabic. He always brings it.
Throw him your staging link.
He'll fetch the bugs before your customers find them. Docs optional.
Start freeFree Starter plan: one module, no card, no time limit.