A browser. A customer journey.
One ordinary browser, one page at a time. It reads the screen, chooses the next click, and keeps screenshots behind its answers.
How it works
Visitor pages
Home, catalog, product, search, cart, sign-in, contact.
Selected devices
One run per check per selected device.
Human pace
One browser per site, one action every few seconds, a few dozen page loads per night, not a crawl.
Runs on our machines
On qa.pro-operated machines, nothing installed on yours.
Reading first. Writing by permission.
Read-only first look
Public pages, browse, search, open product, add to cart, view cart, change the language, open contact page.
First look and first report need no proof.
Sign-in and writing checks
Registration, login, wishlist, password change, form submission, checkout.
Requires ownership proof, a test account entered by the site's admin, and explicit permission. Kept off until provided.
iAt checkout, we stop before payment. No card is entered and no order is placed. Anything beyond that point is only for staging sites the team selects.
Cookie banners may be accepted to view the page. Your settings are not changed.
Devices we can use
- Desktop
- Laptop
- Large desktop
- iPad upright
- iPad lying down
- iPhone 15
- iPhone Pro Max
- Galaxy A
- Galaxy Z Fold closed
- Galaxy Z Fold open
Ten, named as every report names them: Desktop, Laptop and Large desktop; the iPad upright and lying down; the iPhone 15, the iPhone Pro Max and the Galaxy A; the Galaxy Z Fold closed and open. Each is its own browser; every check runs once per device the team ticked. Availability depends on the plan and selected devices.
What it never does
- No orders, payments, or coupon redemption.
- No real customer accounts, customer emails, reviews or comments on a live site.
- No catalogue downloading or content copying.
- No following every link: it stops when the task ends.
- No hiding: qa.pro can identify which browser opened a page and when.
Evidence kept
Screenshots of steps and reasons for the team that requested the check.
How to stop it
| Your site | Pause the site or turn off night schedule in Settings. Removing the site ends future checks. |
|---|---|
| Client site | The team that added the site can pause or remove it. |
| Unexpected visit | Email abuse@qa.pro with the site address and time. We stop it and explain what happened. |
iWriting checks may leave test sign-ups, wishlist items or messages. Remove them like any test data or keep writing checks off.
Proof is part of every report
Every report includes screenshots and a step-by-step trace so you can see what the bot saw and why it clicked. Clients can share report pages with their teams. The engine is built to the rules above. If you see something different, email hello@qa.pro and we will fix it and record the change in the changelog.