lastest

<p align="center">
  <img src="./docs/logo-lockup.svg" alt="Lastest" width="420" />
</p>
<p align="center">
  <strong>Free, open-source visual regression testing with AI-generated tests</strong>
</p>
<p align="center">
  Record it. Test it. Ship it.
</p>

<p align="center">
  <a href="https://lastest.cloud">Website</a> •
  <a href="https://github.com/las-team/lastest/wiki">Wiki</a> •
  <a href="#features">Features</a> •
  <a href="#quick-start">Quick Start</a> •
  <a href="#how-it-works">How It Works</a> •
  <a href="#why-lastest">Why Lastest</a> •
  <a href="#comparison">Comparison</a> •
  <a href="#commands">Commands</a> •
  <a href="#environment-variables">Config</a>
</p>

<p align="center">
  <img src="https://img.shields.io/badge/license-FSL--1.1--ALv2-blue.svg" alt="License" />
  <img src="https://img.shields.io/badge/self--hosted-yes-green" alt="Self Hosted" />
  <a href="https://lastest.cloud"><img src="https://img.shields.io/badge/website-lastest.cloud-0a84ff" alt="lastest.cloud" /></a>
</p>

---

<p align="center">
  <img src="./docs/lastest-intro.gif" alt="Lastest Demo — Record, Test, Diff, Approve" width="720" />
</p>

## The Problem

Visual regression testing is either **expensive**, **flaky**, or **painful to maintain**.

- **Cloud tools**: per-screenshot pricing, cloud-only, no self-hosting
- **Enterprise tools**: steep learning curve, locked to specific frameworks
- **Open-source tools**: free but no dashboard, no collaboration, no AI, or in maintenance mode

Meanwhile, you just need to know: **"Did my last commit break the UI?"**

## The Solution

Lastest is a free, self-hosted visual regression testing platform that **records your tests, writes them with AI, runs them anywhere, and fixes them when they break** — all in one tool.

```
1. Point it at your app
2. Record your user flows (point-and-click, no code)
3. AI generates resilient test code with multi-selector fallback
4. Run on remote runners or in an embedded browser container (EB setup required)
5. Screenshots compared with 3 diff engines (pixelmatch, SSIM, Butteraugli)
6. Review and approve visual changes — or let AI auto-classify them
```

When self-hosted, your data stays on your server and your screenshots never leave your infra.

---

## Three Ways to Work

Lastest adapts to how you want to build tests — from fully manual to fully autonomous.

### 1. AI-Free (Manual Recording)

Open the recorder, click through your app, hit stop. Lastest captures every interaction and generates deterministic Playwright code — no AI involved, no API keys needed. You own the test code and can edit it by hand.

**Best for:** Teams that don't want AI, air-gapped environments, simple flows.

### 2. AI-Assisted (Human-in-the-Loop)

AI generates, fixes, or enhances tests — but you review and approve before anything is saved. Feed it a URL and get a test back. Import OpenAPI specs or user stories and AI extracts test cases. When a test breaks, AI proposes a fix and you decide whether to accept it.

**Best for:** Day-to-day development, iterating on tests, fixing breakages fast.

### 3. Full Autonomous (Play Agent)

One click kicks off an 11-step pipeline: check settings, select repo, set up environment, scan routes & apply testing template, plan functional areas, review plan, generate tests, run them, fix failures (up to 3 attempts per test), re-run, and report results. Uses specialized sub-agents (Orchestrator, Planner, Scout, Diver, Generator, Healer). The agent pauses and asks for help only when it hits something it can't resolve on its own. You resume and it picks up where it left off.

**Best for:** Onboarding a new project, generating full coverage from scratch, CI bootstrapping.

---

## Two Ways to Run

Once your tests exist, you have two execution modes. **Local Playwright execution on the host is no longer supported** — every test runs inside an Embedded Browser pod, so EB setup is required even for development.

| Mode                           | How                                                                                                                                           | When                                                                   |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Embedded Browser** (default) | Browser runs in a container with live streaming back to the UI. Provisioned dynamically into k3d locally, or into your cluster in production. | Default for all dev and prod runs — no local Playwright install needed |
| **Remote Runner**              | Tests dispatched to remote machines via WebSocket                                                                                             | Distributed execution, different OS/browsers, CI/CD                    |

Both modes support **running** and **recording**. Builds can be triggered **manually** (click Run), by **webhook** (PR opened/updated), on **push** to monitored branches via CI/CD (GitHub Action or CLI runner), or on a **schedule** (cron-based automation). Smart Run analyzes git diffs to run only affected tests.

---

## Build Once, Run Forever

Tests are recorded or generated once, then stored as code. Every subsequent run re-executes the same code, captures new screenshots, and diffs them against approved baselines.

- **First run**: screenshot becomes the baseline
- **Every run after**: new screenshot is SHA256-hashed — if it matches the baseline, instant pass (no pixel comparison needed). If it differs, the diff engine runs and you review the change.
- **AI costs are one-time**: AI is only used during test creation and fixing. Running tests uses zero AI — it's pure Playwright execution.
- **No per-screenshot pricing on self-hosted**: every run is unlimited regardless of volume.

```
Create tests (one-time)          Run tests (forever)
┌──────────────────────┐         ┌──────────────────────┐
│ Manual recording     │         │ Execute Playwright    │
│   — or —             │  ────▶  │ Capture screenshots   │
│ AI generation        │  save   │ Diff against baseline │
│   — or —             │         │ Review changes        │
│ Play Agent autonomy  │         │ Approve/reject        │
└──────────────────────┘         └──────────────────────┘
  AI may be used here              No AI needed here
```

---

## Features

### Core

- **Record Browser Interactions** — Point-and-click test recording via Playwright with multiple engines (custom recorder or Playwright Inspector). No code required.
- **AI Test Generation** — Claude generates robust test code with multi-selector fallback (data-testid → id → role → aria-label → text → css → OCR).
- **Multi-Engine Visual Diffing** — Three comparison engines: pixelmatch (pixel-perfect), SSIM (structural similarity), and Butteraugli (human-perception-aligned). Choose the best trade-off between speed and accuracy.
- **Multi-Step Screenshots** — Capture multiple labeled screenshots per test run for multi-page flow testing.
- **Approval Workflow** — Review visual diffs before they become baselines. Catch regressions, approve intentional changes.
- **Check Modes** — Unified verification control across 9 layers (visual, text, DOM, network, console, a11y, design, performance, URL), each set to enforce, log, or disable per repo — replacing scattered per-feature toggles.
- **Verify Board** — Per-step card board for reviewing multi-layer check results: change map, per-layer baselines, and reviewer feedback in one focused view.
- **Design System Verification** — Design-token comparison layer that flags drift from your design system (colors, spacing, typography) as its own check layer.
- **URL Diff** — Capture and diff URL trajectories across runs to catch unexpected redirects and navigation changes.
- **Analyze URL** — Pre-recording selector tuning: scans the target page, measures selector-strategy coverage (data-testid, aria, ids, …), and recommends a priority order matched to your app.
- **Git-Aware Builds** — Run tests per branch/commit. Compare across PRs. Track coverage.
- **Branch Comparison** — Dedicated compare view for side-by-side branch-to-branch test result diffing.
- **Test Suites** — Organize tests into ordered suites for structured execution.
- **Test Versioning** — Full version history with change reasons (manual edit, AI fix, AI enhance, restored).
- **Test Composition** — Cherry-pick tests and pin specific test versions per build via the Compose page. Override latest with any historical version.
- **Functional Area Hierarchy** — Organize tests into nested parent/child functional areas with drag-and-drop reordering.
- **Debug Mode** — Step-by-step test execution with live feedback for diagnosing failures.
- **Testing Templates** — One-click preset configurations for common app types: SaaS/Dashboard, Marketing Website, Canvas/WebGL, E-commerce, Documentation, Mobile-First, SPA, and CMS.
- **Auto-Detect Capabilities** — Recording automatically detects required browser capabilities (file upload, clipboard, downloads, network interception) and enables corresponding Playwright settings.
- **Early Adopter Mode** — Team-level toggle to access experimental features before general release.
- **Scheduled Test Runs** — Cron-based automated builds with preset schedules (daily, weekly, hourly) or custom cron expressions. Auto-disables after consecutive failures. Optional branch targeting.
- **Success Criteria Tab** — Parsed assertion tracking per test: see which `expect()` calls passed/failed with expected vs actual values, error messages, and code line references.
- **WCAG 2.2 AA Compliance Scoring** — Automated 0–100 accessibility score per build with severity-weighted deductions (critical/serious/moderate/minor), trend sparklines across builds, and per-test violation detail.
- **Guided Onboarding** — 8-step setup g