Quality Assurance

/lavra-qa

Browser-based verification from the user's perspective. Catches what unit tests miss -- broken layouts, console errors, dead interactions.

Headless Chromium via agent-browser

Four verification passes

1

Load affected pages

Detect changed routes from git diff

Only tests pages that were actually modified. No wasted cycles on unchanged routes.

2

Check console errors

Flag warnings, errors, unhandled exceptions

Catches runtime errors that pass type checking -- missing API responses, broken event handlers, failed network requests.

3

Test interactions

Forms, clicks, navigation flows

Fills forms, clicks buttons, follows navigation paths. Verifies that the page responds correctly to user actions.

4

Screenshot diffs

Visual regression against baseline

Captures screenshots and compares against stored baselines. Catches CSS regressions, layout shifts, missing elements.

When to use it

/lavra-qa is optional in the pipeline -- use it when visual correctness matters.

Good fit

  • Frontend changes (CSS, layout, components)
  • Form validation or interactive UI
  • Multi-page flows (checkout, onboarding)
  • After dependency upgrades

Skip when

  • Backend-only changes (APIs, services)
  • Config or infrastructure changes
  • Documentation updates
  • No browser-facing code modified