Works / Greenlight · Site QA Automation

The Site QA That Catches What a Global Change Broke

Change one template on a site with hundreds of pages and you can't eyeball them all. Greenlight scans them, compares the new build against the last known-good one, and flags only what actually changed — plus confirms each still loads and its forms still work. No AI, just the same check every run.

Client: Marketing Team · Role: Automation Engineer · Year: 2026 · Stack: Javascript · Playwright · sharp · Google Sheets

The story

The before: You make one global change — a template, a component, a migration — and it ripples across hundreds of pages. Which ones did it quietly break? By hand, that's clicking every URL, comparing against how it used to look, and hoping you didn't miss one.

The turn: So I built Greenlight. It re-checks every page against the last good build, flags the ones that actually shifted, confirms each still loads and its forms still work, and drops a green-or-red result per page in a shared sheet.

How it works

  1. Command: You run one command locally — the whole site, a batch, or a single page.
  2. Playwright: It opens every page like a real browser, on desktop and mobile, and shoots the new build beside the reference.
  3. Compare: Fixed rules diff the two — layout drift, soft 404s, redirects, broken links — and test every form. No AI, so the answer's the same every run.
  4. Google Sheets: One row per page lands in a shared sheet, color-coded green or red, screenshots attached — the team sees what changed at a glance.

A global change is a leap of faith across every page — more than anyone can re-check by hand. This is the net: it re-reads all of them against the last good build, so the pages that broke surface before your visitors find them.

What changed

did my global change break anything? which pages don't match the old build? do the forms still send?

The numbers: hundreds of pages — re-checked in one unattended run.

Fair questions

does it check content, or just that pages load?

Both — it diffs each page against the last good build to catch content and layout shifts, and confirms it still loads without a soft 404 or a redirect. (from the build)

can I just check everything returns 200?

Yes — there's a lighter mode for a quick status pass, or a full staging-vs-production snapshot diff when you need it. (from the modes)

does it touch the live forms?

It tests every form end to end — submits one and screenshots the confirmation email, proof it truly sent. Prefer not to hit the client's inbox? A fill-only mode stops before submitting.

The reel continues

Previous: MARA · Tickets Reporter · Next: MARA · Slack AI Assistant · open my notebook?

Got hundreds of pages to re-check after every change, migration, rebuild, release? Greenlight It — or discover my mastery.