Freelance developers
Know about a broken checkout before your client does, and send them a report that shows the problem, the page and the fix, instead of an apology.
Website QA and testing tool
The website QA tool that finds what is really broken
SourceCode QA is an automated QA tool for websites. It crawls every page, opens it in Chrome, Firefox and Safari's engines on desktop and phone, checks each failure a second time, and turns every real problem into one issue with the page, a screenshot and the steps to see it. Fix it, retest that one issue, and it closes when it is gone.
View a sample report Have us run your site
For freelance developers, agencies and teams who look after websites, their own or their clients'.
Who it is for
Agencies
Every client site tested on a schedule, one issue list per client, and a branded dashboard and report each client can open themselves.
Teams that run a site
Check a release in real browsers before customers do, and keep a record of what broke, who fixed it and whether it stayed fixed.
From finding a problem to fixing it
Run
Crawls and browser tests run on a schedule you choose, after a deployment, or when you press the button.
Review the evidence
Each problem is one issue: the pages, the browser and device, the exact error, a screenshot and the steps to see it yourself.
Fix
Assign it, set a due date, and start with the report's short list, ranked by severity, certainty and whether it touches checkout or accounts.
Retest that one issue
Test only its pages, in only its browsers, without waiting for the next full run.
Track it
It closes only when a test that loaded its pages could not find it. If it comes back later, it reopens by itself, marked as a regression.
See it in a sample report: severity, pages, browser and device, screenshots, the steps to see each problem, and what to fix first.
Fewer false alarms, nothing hidden
A crawl asks for more pages in ten minutes than a site normally serves in an hour, so some of what it sees fail is its own weight. Ask again an hour later and most of it answers perfectly.
What is left can still be wrong. A page can fail for one country and work everywhere else, and a tool that only looks from one place cannot tell you which. That is the difference between "your magazine is down" and "your magazine is down for readers in Germany". Only one of those helps the person who has to fix it.
So a page is only called broken once a second machine, on another continent, has agreed. One that fails in one place only is still reported, labelled as exactly that.
What the QA tool checks
Crawls the whole site
Every page, every link, every form and every asset, following links and the sitemap. It records what each page returned, what it links to, what changed since last time, and which pages are in the sitemap but linked from nowhere.
Opens pages in real browsers
Chromium, Firefox and WebKit (the engines behind Chrome, Firefox and Safari), on desktop, tablet and phone. It watches for JavaScript exceptions, console errors, failed requests, mixed content, layout that scrolls sideways, controls too small to press, images that do not load, and text nobody finished writing.
Checks a failure twice before calling it one
A crawl asks for more pages in ten minutes than a site normally serves in an hour, so some of what it sees fail is the crawl's own weight. Every failed page is asked again later, slowly, and only what fails again is reported as broken.
Asks from somewhere else, and says what it found
A page that will not load is fetched again from a second location on another continent. If it works there, it is not hidden: it is reported as failing from one location only, because that can still mean real visitors there are being turned away.
Keeps one issue per problem
The same fault on forty pages is one issue with forty pieces of evidence, not forty things to read. Issues stay open until a test sees them gone, and reopen by themselves if they come back.
Shows the evidence
Every finding carries the page, the browser, the device, the exact message and a screenshot of the moment. Each issue says how sure we are it is the site's fault, and why.
Walks through key journeys
Sign-in, forms and checkout, step by step in a real browser. Payments use the payment provider's test mode, and on a live site a journey that would change anything runs only after a written sign-off.
Reports your clients can read
Branded HTML and PDF reports, CSV and JSON exports, share links that expire, and a monthly email with the version each reader's role allows.
Real browsers, not a guess
Chromium, Firefox and WebKit (the engines behind Chrome and Edge, Firefox, and Safari), on desktop, tablet and phone. The same page can be perfect in one and broken in another, and the one it breaks in is usually the one nobody on the team uses. Every finding says which.
A QA tool for agencies
Each client has their own account, dashboard and reports, with your branding and on an address of your choosing. Their people can be given their own sign-ins, and see only their own sites. We set the branding and address up with you.
Plans and prices
Priced per account, per month, excluding VAT, with sites included. A site is one address we test, so staging and production are two. Page checks are shared by every site in the account. Limits are what the platform enforces, not a sales sheet.
Starter
€29 a month
One site you want watched.
- Sites included
- 1 (no extra sites)
- Page checks
- 3,000 a month, shared by all your sites
- Pages per crawl
- Up to 250
- Crawl schedule
- Weekly or monthly
- Crawls you start
- 1 a day
- Browser tests
- Up to 50 pages in 2 browser and device combinations, 3 a day
- Results kept
- Last 4 crawls and 4 browser tests per site
Standard
€79 a month
A few sites, checked daily, tested whenever you push a change.
- Sites included
- 3, then €15 a month each
- Page checks
- 20,000 a month, shared by all your sites
- Pages per crawl
- Up to 1,000
- Crawl schedule
- Daily, weekly or monthly
- Crawls you start
- 3 a day
- Browser tests
- Up to 250 pages in 4 browser and device combinations, 10 a day
- Results kept
- Last 12 crawls and 12 browser tests per site
Pro
€199 a month
A business with several sites, or one large one tested hard.
- Sites included
- 10, then €12 a month each
- Page checks
- 75,000 a month, shared by all your sites
- Pages per crawl
- Up to 5,000
- Crawl schedule
- Daily, weekly or monthly
- Crawls you start
- 10 a day
- Browser tests
- Up to 1,000 pages in 6 browser and device combinations, 20 a day
- Results kept
- Last 52 crawls and 52 browser tests per site
Agency
€399 a month
An agency looking after many client sites, with reports in your name.
- Sites included
- 25, then €9 a month each
- Page checks
- 200,000 a month, shared by all your sites
- Pages per crawl
- Up to 5,000
- Crawl schedule
- Daily, weekly or monthly
- Crawls you start
- 20 a day
- Browser tests
- Up to 1,000 pages in 6 browser and device combinations, 50 a day
- Results kept
- Last 52 crawls and 52 browser tests per site
- For your clients
- Your branding and address on their dashboards and reports
Working it out
An agency looking after 15 client sites: Agency is €399 a month, about €27 a site, with 200,000 page checks to share. On Standard the same 15 sites would be €79 + 12 extra sites × €15 = €259 a month, sharing 20,000.
How far page checks go: testing 50 pages in two browsers once a week uses about 400 a month.
Nothing is billed on top without you choosing it: a limit stops at its cap. Free trials open soon. Journeys, performance, security and visitor monitoring are set up with us for each site; ask us what your site needs.
Questions
- What is a website QA tool?
- Software that tests a website the way a careful tester would, on every page and on a schedule: links that go nowhere, pages that error, scripts that crash, layouts that break on a phone, forms and checkouts that stop working. This one also rechecks each failure before reporting it, so what reaches you is a real problem.
- Is the price per site or per account?
- Per account. Each plan includes a number of sites, and on every plan but Starter you can add more at the plan's extra-site price.
- What counts as a site?
- One address we test. Staging and production are two sites, and so are two shops on different domains.
- What is a page check?
- One page loaded in one browser on one device. Testing 50 pages in Chrome on a desktop and Safari on a phone is 100 page checks. Your plan's checks are shared by all your sites and renew on the 1st of each month. Crawls do not use them.
- What happens when I run out?
- A browser test that would go past what is left is cut down to fit, and once none are left, browser tests wait for the 1st of the month. Nothing is billed on top without you choosing it, and you can move to a bigger plan at any time.
- Can I try it first?
- Open the sample report to see what you would get, or send us a site and we will run it and show you what we find. Free trials open soon.
- Why do I have to prove I own the site?
- So nobody can point our tests at a site that is not theirs. Add a DNS record, upload a small file or add a meta tag, once per site, and testing starts.
Already using Monitrova?
They do different jobs. Monitrova checks often whether your site is working right now, and tells you the moment it is not. SourceCode QA looks deeper and less often: what is broken, where, with the evidence, and whether a fix worked. They are separate products and do not share data.
Talk to us
Tell us the site and what worries you about it, and we will run it and show you what we find. Get in touch, or open the sample report first.