Repository navigation
v0.8.0 — smoke test: open the app in a real browser and look
Smoke test — open the app in a real browser and look. One new skill answers
"does the app run": it asks what to check, asks before it starts Docker and
Chrome, visits each page once and saves a picture of every one.
Added
/pspt:smoke— offers the pages to check from the frontend router, the
spec's screens and local HTML files (email previews), then asks once for
permission to run Docker and Chrome for this run. It uses the app if it is
already running, otherwisedocker compose up -d --wait; logs in with a
throwawaysmoke+<time>@example.testuser when a page needs it; visits each
page once; and saves a full-page PNG of each. A page fails on an HTTP error,
an uncaught JavaScript error, a failing or5xxrequest to the app's API, a
console error, a missing element or a login redirect — and the assistant
reads every picture, so a blank page or a broken layout fails too. The test
user is always deleted, and only what the skill started is stopped.references/smoke/smoke.mjs— the runner: Playwright from the project
first, then a global install; Google Chrome first, then Playwright's
Chromium. Writes the PNGs andreport.jsonto.pspt-smoke/<run>/, which is
excluded from git. Exit0pass,1fail,2no browser.
Limits, stated in every report
- Local only: never production or staging, never a migration outside the local
container, never a deploy, never a real email or payment. - Desktop Chrome only — not how Gmail or Outlook render an email, no
email-client dark mode, no WebP handling of mail clients. - One visit per page — a smoke test, not a test suite. Failures are offered as
a/pspt:ticket; the skill never edits code.
Full history: CHANGELOG.md
