What changed, newest first.
Every change a customer can see lands here with its date. Fixes to the engine's checks are listed when they change a verdict you could have seen.
The log starts with this week; older changes were not written down for readers and are not made up here.
- A bell in the header. A dot on it means something is new for your team since you looked: a report that found something different, a site that passes again, a check that waits for an admin. Press it for the list; on a phone it opens a page.
- One colour. qa.pro's mark is the blue of its buttons; green means a check passed.
- The Overview answers first. One line at the top says whether your sites are OK; under it, what is being checked this minute, with the browsers' screens while a report runs and a countdown to the night's report while it is quiet; then what broke, with the pictures; your sites as states; and what happened, with times. A site that ran out of time is "not fully checked", never "failing".
- A new mark. qa.pro has a new mark, a hawk's eye in a window, and its name is written beside it. The front page says in one sentence what it does; under the box the arrow points at the next screen from the bottom of yours.
- One look. qa.pro is light for everybody.
- Light by default. qa.pro opens in the light theme for everybody; the dark one is a press away, on the switch in the header, which is larger and says what it does.
- Re-check and a site's proof. Re-check no longer takes a site's proof when the site does not answer for a moment. If a site's proof goes missing, the team's admins get a mail and the Overview says since when.
- Alert mails. An alert mail says which report it is about, and what passes again. The same failure is mailed once, not again after every report. Your own address gets your team's alerts from the first report on, until you change the list in Settings.
- A check, step by step. The step-by-step view of a check keeps one size while it plays and shows a phone's pictures three in a row on a wide screen; the live view lists the checks done, the one running and the next five.
- Your account. Your account page has 'Log out on every other device'.
- The front page on a tall screen. The first screen ends on the next heading, not on a picture cut by the window's edge; each picture rises into place as you scroll to it.
- One look for everybody. qa.pro opens in the same theme on every device, whatever the browser's own; the switch in the header changes it for your browser.
- The audit log on a phone. Each entry shows its time, who, what, the target, the detail and the address under their names; nothing scrolls sideways.
- Adding a site is paused. While the report is rebuilt, a new site cannot be added. The sites a team has are checked every night as before; the front page's box shows a look at qa.pro itself, and a new team's 14 days start with its first site.
- What needs your proof. Night reports, and every check that signs in or writes, run only on a site its team has proven. A first look and a first report read a site's public pages without it. The security page and the bot's page say so.
- What we keep, said as it is. The privacy page names what a report keeps (a screenshot of each step, the logs), for how long on each plan, and that a look without an account is erased after 3 days.
- Not checked is not passed. A check our browser could not judge is shown as not checked, never as passed or failed; a site with such checks gets no green.
- Pricing. Extra sites and yearly billing are arranged by mail; the FAQ says what happens when site-runs run out and that a staging counts as one of the plan's sites.
- Light and dark, and phones. A switch in the header chooses the theme; the Checks page, the Reports list and Members fit a phone without a sideways scroll.
- Plans. Shop $15 (one store), Solo $29 (5 sites), Team $99 (20 sites, unlimited members), Agency $249 (50 sites, your name and logo); every paid plan covers every site, every night, on desktop and phone. Existing teams keep their plan.
- The client's report page no longer invites your client to buy qa.pro. It reads "Prepared by your team · checked with qa.pro", names the checks that were not on the site, and shows one failing screenshot at full width.
- Keep a report you started from the front page in a team you already have: the site, its first look and the running report move over; a site you already watch gets the new report next to its old ones.
- The front door. Paste an address without an account, watch the first look and the first report live, then keep it with a 14-day Team trial. The live page says plainly when a private address cannot be reached from the internet.
- One set of numbers. The overview, the report, the client's page and the alert count the same checks; "not on this site" is kept apart from "not in this report"; the report's clock is shown only while it is at least as long as its longest check.