Build nearly complete — validation in progress

CapAI Webpage Regression Bot

Website releases can introduce hidden functional, visual, navigation, flow, typography, responsive, browser, accessibility, SEO, security and performance regressions.

Representative image

Prototype evidence or graceful placeholder

Approved prototype image or placeholder for CapAI Webpage Regression Bot

If an approved prototype image is unavailable, the PAL placeholder is shown deliberately instead of a broken-image icon.

Context

Who it serves and what it addresses

Baseline-led website discovery and regression assurance across routes, features, tabs, user flows, fonts, visual differences, responsive layouts, browser compatibility, accessibility, performance, APIs, security smoke checks, evidence and release gates.

Intended users: Website owners, quality engineers, release managers and product engineering teams
Data dependencies: Accepted deployment packages, checksums, route and API inventories, visual baselines, browser-test evidence, accessibility results and performance measurements.
Last reviewed: 2026-07-05

Architecture relationship

How the capability connects

Agent Hub: Can use governed agent assistance for feature discovery, test-case suggestions and failure summaries, while deterministic test execution remains authoritative.

Engineering Control Center: Designed as a protected Regression Testing capability within the Engineering Control Center, with CI-based execution and an evidence-led release-gate view.

Uses CI or a developer-controlled runner for browser execution; the Engineering Control Center presents protected coverage, evidence, manual gates and release decisions without turning the production Worker into a test-execution server.

Governance and publication

Control and confidentiality boundaries

Deterministic test results and accepted baselines are authoritative. AI may assist with discovery and summarisation but cannot change test results, approve visual differences or release a deployment.

No credentials, private repository tokens, raw production data, unrestricted screenshots or detailed private test artifacts are exposed through the public website.

Publication boundary: Public product description only. Implementation details, baselines, screenshots, traces and validation evidence remain protected.
Source availability: Not publicly available
Future direction: Finish validation and integrate the approved regression summary into the protected Engineering Control Center before any production claim.