Introducing Test Tools: a built-in QA toolbox inside Arqo

QA engineers live in a dozen browser tabs — a JSON formatter here, a base64 decoder there, a link checker, a DNS lookup, a regex tester. We brought the most useful ones into Arqo, right next to your test cases. Meet Test Tools: nine utilities, one tab, no context switching.

Why we built Test Tools

Test management isn't just writing and running test cases. Before you sign off a release you're checking that links work, headers are set, the staging environment is up, the copy reads well, and the payload decodes the way you expect. Each of those is a quick job — but each one usually means leaving your test tool for some random site you half-trust with your data.

Test Tools puts those jobs inside the project you're already working in. Open any project, click the Test Tools tab, and pick a tool from the sidebar. The URL-based checks run on Arqo's servers; the rest run entirely in your browser. Nothing is stored.

Site & infrastructure checks

Website Scanner

Point it at any URL and get a full readout: HTTP status, response time, SSL certificate validity and days remaining, detected tech, the redirect chain, and response headers — followed by a graded audit across three areas, each scored 0–100.

• Security headers — HSTS, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy and HTTPS
• SEO — title, meta description, canonical, viewport, Open Graph, html lang and a single H1
• Page health — status, page size, mixed (insecure) content, link counts and redirects

It's the fastest pre-release sanity check we know of — and if something's wrong, you can raise a Jira defect straight from the finding (more on that below).

Broken Link Checker

Crawls every link on a page and checks each one's reachability, listing broken links first. It uses a HEAD request (falling back to GET) and checks links concurrently, so even a link-heavy page comes back in seconds. Catch your 404s before your users — and your stakeholders — do.

DNS Lookup

Resolve a domain's A, AAAA, CNAME, MX, TXT, NS and SOA records, plus its registration details via WHOIS/RDAP — registrar, registered and expiry dates, and status. It also geolocates the resolved IP on a map and shows the owning org and ASN, so you can see at a glance where a site is actually served from.

Content & defects, powered by AI

Proofreader

Paste a URL and Arqo's AI reads the page's visible copy, flagging spelling, grammar, punctuation and style issues with suggested fixes and surrounding context. Content bugs are still bugs — this catches the ones a functional test never will.

Bug Report Writer

Type your rough notes — 'clicked save on mobile safari, page froze, lost my changes, happens every time' — and get back a clean, structured defect: title, severity, environment, steps to reproduce, and expected vs actual. Copy it as Markdown straight into your tracker. It turns the messiest five-second observation into a report a developer can act on.

Everyday developer utilities

Four classic, no-nonsense tools that run entirely in your browser:

• JSON Formatter — pretty-print, validate or minify, with exact line/column on parse errors. Perfect for eyeballing an API response.
• Test Data Generator — pick fields (or a preset like User/Account/Payment), set a row count, and generate a table of realistic records you can copy as JSON or CSV.
• Encoder / Decoder — Base64, URL and HTML entities with live conversion, plus a JWT decoder that shows the header, payload and expiry.
• Regex Tester — test a pattern against sample text with live match highlighting, flag toggles and a capture-group breakdown.

Raise a Jira defect in one click

The Website Scanner and Broken Link Checker don't just find problems — they help you file them. Hover any failing check or broken link, click Report, and Arqo opens a defect form pre-filled with the URL, the finding and its details. Pick your Jira connection, tweak the summary, and create the issue without leaving the page.

Private by design

The server-side tools enforce an SSRF guard — no localhost, private IP ranges or non-standard ports — and a request timeout, so they can't be turned into a port scanner. Results aren't persisted; they live only in your browser session until your next check. The in-browser tools never send your data anywhere at all.

Where to find it

Open any project and select the Test Tools tab. Each tool has a 'How it works' link to its documentation if you want the detail. We're just getting started here — scheduled scans, Lighthouse-style performance scores and a first-class accessibility audit are on the roadmap.