A browser opens your site and uses it like a customer. Here is exactly what that means.
One ordinary browser, one page at a time, a few dozen pages a night. It reads the screen, decides the next click, and keeps a screenshot behind every answer. This page says what it opens, what it clicks, what it never does, and how to stop it.
What it opens
- Pages
- the home page, a category or listing, a product or article, the search results, the cart, the sign-in page, the contact page: the pages a visitor opens
- Devices
- a desktop window and a phone-sized one, each its own browser; every check runs once per device the team ticked
- Pace
- one browser per site, one action every few seconds, about the pace of a person; a night's checks are a few dozen page loads, not a crawl
- From where
- machines qa.pro operates in the United States, never yours; the first look and the first report a visitor asks for read a site's public pages without proof; everything after them runs only after its owner proved the site is theirs (a file, a meta tag or a DNS record)
What it clicks
- Reads only
- search for a product, open it, add it to the cart, look at the cart, browse a category, follow the logo home, change the language, open the contact page: these leave nothing behind and are on from the first look
- Writes
- sign up, sign in, save to a wishlist, change a password, send the contact form, go to checkout: each of these needs a test account the site's admin entered and the admin's say-so; until then it stays off
- Checkout
- it goes as far as the payment step and stops: it never enters a card and never places an order; anything past that point runs only on a staging site the team points it at
- Consent
- it accepts the cookie banner the way a visitor would, to see the page behind it; it does not change any setting of yours
What it never does
- Orders
- no order is placed, no payment made, no coupon redeemed
- Your customers
- it never touches a real customer's account, never sends them mail, never posts a review or a comment on a live site
- Your data
- it does not download your catalogue or copy your content; what it keeps is the screenshot of each step and a one-line reason, for the team that ordered the check
- Crawling
- it does not follow every link; it follows the few a customer would to finish one task, then stops
- Hiding
- it runs a plain browser, and qa.pro can say which of its browsers opened a page and when
How to stop it
- Your own site
- pause the site or turn the night schedule off in Settings; removing the site ends every future check the same minute
- A site you run for a client
- the team that added it can pause or remove it; the report page tells you which team that is
- A site you did not add
- qa.pro never opens a site that was not proven to belong to the team that added it, beyond one first look and one first report; if you still see us where you should not, write to abuse@qa.pro with the address and the time, and we stop it and tell you what happened
- Test entries
- a check that writes uses the test account you gave it and may leave a test entry (a wishlist item, a message, a test sign-up); delete them like any test data, or keep the writing checks off
Why you can believe this
Every check keeps its screenshots and the steps it took; the team that ordered the check sees them on the report, and a client sees them on the report page the team shares. There is nothing the bot does that does not end up on that page. The rules on this page are the rules the engine is built to; if you find it doing otherwise, write to hello@qa.pro and we fix it and say so in the changelog.
Also
Security: how test accounts and screenshots travel. Privacy: what we store. Data processing: the agreement for teams that need one.