Tester: Clear PASS or FAIL Results With Screenshots
Every check comes back PASS or FAIL, with the screenshot to prove it.
The Tester is the AI website testing agent in the Ai1 platform by MyZone AI that opens a real browser, steps through your site or app at desktop and mobile screen sizes and reports every check as a numbered PASS or FAIL with screenshots, without changing the work it checks.
Each change is checked before it counts as done, so broken pages and failing forms are caught before real visitors meet them.
Verdicts you can act on at once
A clear PASS or FAIL with evidence replaces a vague looks fine, so fixing can start the moment something is wrong.
Fixes that do not break something else
After a fix, it checks the surrounding features too, so a repair in one place does not quietly cause a problem next door.
Nothing assumed
If the expected behaviour is unclear, it asks before it tests, so every check is deliberate rather than a guess.
Meet your agent
Get to know Sana
Sana checks that your site and code actually work, and gives you a clear PASS or FAIL with the evidence to prove it. She is sharp, fast and loves breaking things on purpose.
AI agent. Fictional persona; not a real person.
Sana, the persona of the Tester
Name
Sana M.
Role
Software Tester
Experience
4 years
Work history
QA engineer at an e-commerce startup Test analyst at a software house
Personality
Sharp, clear verdicts
Based in
Karachi, Pakistan
Why Sana has a personality
AI does better work as a specific expert, so the Tester works as Sana (Software Tester, Karachi, Pakistan). You can rename Sana or change the personality, experience and profile settings at any time.
Desktop and a mobile size of 375 by 812 pixels, in a real browser
What it checks
Layout, buttons, forms and links, your automated tests and every fix
On request
Core Web Vitals, page speed and WCAG 2.2 AA accessibility
Each result
A numbered PASS or FAIL, with expected versus actual for every failure
What it never does
Fix product code: failures go back to your developer
Capabilities
What the Tester does for you
Checks pages in a real browser
Real browser testing: it sets the screen size, opens the page and checks that it looks right and that buttons, forms and links work, on both mobile and desktop.
Runs your automated tests
It runs your project's test suite and reports every result. Anything that fails comes with the full error output, so your developer knows exactly what to fix.
Sweeps for knock-on breaks after a fix
Once a bug is fixed, it confirms the fix and then checks the features around it to make sure nothing nearby broke.
Reports with evidence
Every verdict lists numbered test cases, shows expected versus actual for each failure and includes screenshots, so there is no doubt about what passed.
Checks speed and accessibility
Before a launch or after a redesign, it can run Core Web Vitals and page speed checks and audit pages against WCAG 2.2 AA accessibility.
Writes new test code when you need it
If a check needs a new automated test, it writes one in your project's test framework, runs it and reports the result. It writes test code, never product code.
How the Tester differs from a quick look in your own browser
A quick look in your own browser tells you a page seems fine on one screen. The Tester sets the screen size, steps through the page like a visitor at desktop and mobile sizes and records a numbered PASS or FAIL for every check, with screenshots and expected versus actual for each failure. After a fix it sweeps the features nearby, and it never changes the work it checks.
How this differs from the QA Orchestrator: the QA Orchestrator decides how deep to check a change and combines the Tester's results with other specialists' into one verdict, while the Tester runs the browser checks and test suites.
How it works
From your request to a finished result
It runs inside your Ai1 system and works in the tools you already use. You ask, it works, it reports, and it stops for your OK where it matters.
Tap the diagram to enlarge it
Step 1: Take the brief
You share the page address, the behaviour you expect or the test to run. If anything is unclear, it asks before starting.
Step 2: Set up the session
It sets the right screen size and, for browser checks, reads the acceptance criteria from your project documents.
Step 3: Run the checks
It navigates, clicks, fills in forms, runs tests and captures screenshots, recording a result for every case.
Step 4: Compile the report
It closes the browser and builds a numbered PASS or FAIL report with screenshots and error details.
Step 5: Hand back the results
You get the full results. When several checks run together, the QA Orchestrator combines them into one verdict, and failures go to your developer.
When to use it
Hand these situations to the Tester
Illustrative photo. Asking whether the new booking page works on phones as well as laptops.
If this is you…
…here's what it does
A developer says a change is ready
It steps through the expected behaviour in a browser and returns a verdict with screenshots before you mark the work done.
You want to see how a page looks on mobile
It switches to a mobile screen size, checks the layout and interactions, and captures a screenshot.
A bug was fixed and you want to know nothing else broke
It confirms the fix, then checks the surrounding features at both mobile and desktop sizes.
You want your automated test suite run
It runs the tests, reports every result and includes the full error output for anything that fails.
A launch or redesign is coming up
It runs speed and accessibility audits and gives you the results to act on before visitors arrive.
What you get
A numbered PASS or FAIL list covering every check
Screenshots at desktop and mobile screen sizes
Expected versus actual for each failure
Full error output from automated test runs
Core Web Vitals, page speed and accessibility results when requested
What it won't do
✕Fix application bugs or write product codeHandled by: The Developer
Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended.
What it was asked: Check our booking page on desktop and phone before release, and tell us which issues must be fixed first.
Example report
Release verdict and three findingsExpected versus observedDesktop and phone evidenceFix and retest plan
What it found: 3 findings, with the numbers
Submitting without a preferred date shows “Request sent” instead of stopping the request.
The service card says CAD $95, while the booking summary says CAD $80 for the same selection.
At 375 px wide, page content measures 759 px, leaving 384 px of horizontal overflow.
Tester ran six deterministic browser checks on one disposable synthetic local booking page at desktop and phone widths, and captured the two rendered views. The three failures are real observations of deliberately seeded faults in that fixture, not claims about a client site; the front-end confirmation did not send a booking to a server. No production system or personal data was touched, and the browser was closed. Run date: .
Want a release check like this for your own site? Book a Tester walkthrough.
Maintains the skills and tools your agents use; the Tester checks that features built with them behave.
Common questions
Frequently asked questions about the Tester
Why test a website in a real browser?
Because that is where visitors meet it. Browser testing opens the page, sets the screen size and checks that it looks right and that buttons, forms and links work. The Tester in Ai1 by MyZone AI does this at desktop and mobile sizes and records a numbered PASS or FAIL for every case, with screenshots.
For mobile it uses a real browser set to a screen size of 375 by 812 pixels, which catches the vast majority of layout and interaction problems. It does not run on physical devices.
What should a pass or fail test report include?
A numbered list of every check with its result, expected versus actual for each failure, screenshots at the sizes tested and any raw error output. That is what the Tester hands back, so your developer can start fixing at once.
The Tester does not repair what it finds. Its job ends at the verdict and the evidence, which keeps the check independent.
Can automated QA testing check page speed and accessibility?
Yes. Before a launch or after a redesign, the Tester can run Core Web Vitals and page speed checks and audit pages against WCAG 2.2 AA accessibility, alongside its browser checks and your automated test suite.
What if I am not sure what to test, and can the Tester write new tests?
Tell it what you changed or what worries you. If that is too vague for a reliable check, it asks one or two questions first. It never guesses.
If you need a new automated test for your project's test framework, it writes it, runs it and reports the result.
About Ai1
Do I get just the Tester, or the whole platform?
The whole platform. The Tester is included on every Ai1 level, including Developer Core, with no per-agent charge. It works alongside the other Ai1 agents on your account. Compare plans →
Two paths, one platform. Build it yourself on a developer plan, or let our team run your AI operations for you. Every plan runs on its own private server, and every price is shown in full. See Ai1 pricing →
Product & Engineering
Product & Engineering
Product & Engineering
Product & Engineering
Product & Engineering