Run Test – QA Runner

QA Runner

Run Test Reports

Run a new test

Results are saved under the Jira task ID and accessible from Reports.

Jira Task ID Required

Used to group and identify this test run in Reports.

Run By Required

Attributed on every report, so teammates know who ran it.

Test Type

Accessibility + SEO

axe-core a11y scan, meta tags, OG tags, headings, canonical

BTS1 + BTS2 + BTS3

Screenshots

Full-page captures at selected breakpoints

Visual

Breakpoints

375px — Mobile 768px — Tablet 1440px — Desktop 2200px — Wide 2500px 4K (3840px)

Browsers

Chromium (Chrome) WebKit (Safari)

Environment Required

Dev/Stg Prod

Performance score

Performance, SEO, Best Practices, and Accessibility scores (0–100)

Perf · SEO · BP

Backend

Lighthouse

PageSpeed Insights

Lighthouse runs locally — works on any URL, including localhost.
PageSpeed Insights runs on Google's servers — requires a public URL, returns the canonical pagespeed.web.dev score.

GEO Readiness

AI crawler access, schema markup, and content structure

GEO

URLs

Single URL

Multiple URLs

0 of 10 URLs Max 10 URLs — remove some before running.

One URL per line. Blank lines are ignored.

Baseline Test Suite

BTS1

Component

Component-level accessibility and interactions — structure, ARIA usage, keyboard reach, focus order.

ARIA roles Focus order Keyboard nav Colour contrast Duplicate IDs

BTS2

Content

Authored page quality — SEO meta, OG tags, headings, image alt text, and link integrity.

Meta description OG tags h1 + heading order Alt text Tag Manager

BTS3

Page Structure

Structural elements and landmarks — charset, viewport, lang attribute, canonical, robots meta.

Landmarks Canonical Viewport Lang attr Charset

When to use each

Component creation

Authoring content

CMS / page structure

LP creation / deploy

Audit

The Accessibility + SEO test type runs axe-core checks (BTS1 · Component Accessibility) plus BTS2 · Content Quality and BTS3 · Page Infrastructure checks.