SiteLens QA · SiteLens Platform engine

Verify real workflows—not just individual pages.

Run real Chromium workflows with SiteLens Local for free against localhost, staging, and private URLs—or use SiteLens Cloud/API for hosted execution, persisted runs, and team-visible history. Chain setup, state initialization, and validation flows in a shared browser session with Scenario Runner. Capture screenshots, console and network signals, stepped scenarios, matrices across surfaces, and structured artifacts for operational regression workflows.

SiteLens Local Local vs Cloud/API Cloud dashboard Recent Cloud runs
Run artifacts — screenshots, findings, and step timeline
Matrix / viewports — desktop and mobile coverage

Flagship QA templates

Implemented today

Real product capabilities in SiteLens Studio—not roadmap slides. Pick a template, run against your URL, and get structured summaries, named screenshots, and dedicated result panels above the step timeline. Use SiteLens Local for free or SiteLens Cloud/API when you need persisted history.

Internal Link Health

Navigation

Check internal links without writing a crawler.

Crawl a limited set of internal links on desktop—validate each destination loads, surface HTTP and routing failures, and review a dedicated link-health panel with failed URLs and counts.

  • Bounded link set—not a site-wide recursive crawl
  • Screenshots and structured pass/fail per link
  • Ideal after deploys or nav refactors

Mobile Navigation Validation

Mobile

Verify your mobile menu opens and exposes navigation.

On a 390×844 mobile viewport, detect a likely menu trigger, open it, and confirm navigation content is visible—with before/after screenshots and clear failures when no toggle or drawer appears.

  • Trigger found · menu opened · nav visible
  • Mobile navigation result panel in QA Studio
  • No brittle “click every link” scripting

Deployment Verification

Deploy

Confirm a deploy loads on desktop and mobile.

Post-deploy smoke on desktop and mobile: page load sanity, visible body, heading or main landmark, stable screenshot slugs (deployment-desktop, deployment-mobile), and pass/fail suited to CI gates.

  • Desktop and mobile viewport checks in one flow
  • Console and network rollup when issues appear
  • Deployment result panel with per-viewport status

Also available: Homepage Smoke, Navigation Health, and lightweight Accessibility Smoke templates. For multi-step authenticated journeys, see Workflow Verification below. Open QA Studio to start from a template catalog.

Workflow Verification

Scenario Runner

Most browser QA tools stop at a page. Real applications require setup. SiteLens reuses saved browser profiles, initializes application state, runs setup flows, and verifies the workflow your users actually follow—all in one shared browser session.

Scenario Runner

Chain reusable flows from .sitelens/flows/ into scenarios under .sitelens/scenarios/. Login, initialize state, open a workflow, perform actions, and verify outcomes—without restarting the browser between steps.

  • Saved auth profiles under ~/.sitelens/profiles/
  • Parameterized flows with params and {{placeholders}}
  • MCP tool sitelens_run_local_scenario and CLI sitelens run scenario

Built for authenticated applications

Ideal for SaaS dashboards, admin interfaces, internal business apps, role changes, feature toggles, setup flows, and post-deployment verification beyond page-load smoke.

  • Authenticated dashboards and multi-step user journeys
  • Shared cookies, local storage, and session state
  • Onboarding paths, admin workflows, and smoke verification chains

See the Scenario Runner guide, login-once auth, and QA Studio scenarios.

SiteLens Local on the QA engine

Free · no API key

SiteLens Local is free local execution on your machine—not a limited SaaS tier. Bundled Chromium reaches localhost, VPN staging, and private URLs without sending traffic through SiteLens Cloud/API.

  • No API key required for Local runs
  • Real Chromium execution with local screenshots and reports
  • Scenario Runner: chain flows in a shared session with saved auth profiles
  • localhost, staging apps, and auth session reuse (Playwright-style state where supported)
  • Pair with SiteLens MCP in Cursor or your own scripts

What SiteLens QA gives you

Workflow Verification

Run setup, verification, and validation flows in a shared browser session—perfect for authenticated applications, role changes, feature toggles, and multi-step workflows.

Real Chromium

Production-style browser QA on SiteLens Local and SiteLens Cloud/API—with artifacts you can inspect and share.

Local + Cloud/API

SiteLens Local for private hosts and Scenario Runner; SiteLens Cloud/API and SiteLens Studio for hosted monitoring, CI, and team workflows.

Screenshots & evidence

Named screenshots and step-level outcomes alongside structured summaries—ideal for triage after deploys or UI changes.

Flagship templates

Internal Link Health, Mobile Navigation Validation, and Deployment Verification—ready in SiteLens Studio with dedicated result panels.

Saved auth profiles

Login once and reuse browser sessions across flows and scenarios—cookies, local storage, and authentication persist through the workflow.

Matrices

Exercise combinations—viewport, route, or data slices—without losing step-level transparency.

Persisted Cloud/API runs

When the API persists, hosted runs become durable objects you can list, diff, and reference across sessions.

SiteLens Local vs SiteLens Cloud/API

Execution modes

Two execution modes on one QA engine—pick SiteLens Local for free dev workflows; SiteLens Cloud/API for persisted runs, CI pipelines, and team history.

SiteLens Local

Free local execution
  • Developer machine execution
  • localhost, staging, private URLs
  • Auth session reuse where supported
  • No API key · IDE/MCP-friendly dev loops

SiteLens Cloud/API

API key
  • Hosted runs on public URLs
  • Persisted runs, screenshots, and run history
  • CI/CD and deployment verification
  • Monitoring direction and team workflows (schedules as you adopt them)
Aspect SiteLens Local SiteLens Cloud/API
Cost Free local execution Usage tied to workspace / API key
Targets localhost, staging, private LAN from your machine Public URLs reachable by SiteLens
Runtime Bundled Chromium on your workstation Hosted Chromium clusters
Artifacts Local screenshots + reports under your artifact dir Persisted runs, screenshots, MCP sitelens://runs/{id} when enabled
API key Not required for local runs Required for cloud/API and dashboard workflows
Typical use Pre-push checks, localhost QA, private env validation Monitoring, scheduled scans, CI, team triage
Docker Neither path requires Docker on your workstation.

Scenario Runner is available today via SiteLens Local and MCP—chain parameterized flows in a shared browser session with saved auth profiles. Cloud-hosted scenario orchestration in QA Studio is evolving.

Interaction QA—not just uptime

Example: open a reader, select text, apply a highlight, assert markup, capture desktop and mobile shots—scenario highlight-preamble-apply-blue.

desktop: passed mobile: passed

assert exists [data-testid="highlighted-text"]

Example API calls

US Constitution highlight demo

curl -s -X POST https://api.sitelensapi.com/demo/usconstitution-highlight | jq

Generic QA request

curl -s -X POST https://api.sitelensapi.com/analyze/qa \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com",
    "viewports": ["desktop", "mobile"]
  }' | jq

Where to go next

Stay in the loop

Contact us about SiteLens QA—localhost runs, Cloud/API workflows, onboarding, or product updates—the same form as our homepage.