Self-hosted verification for manual regression

Verify what you’d have shipped.File the proof.

A self-hosted runner for manual regression passes. Step through a deck of test cases, mark each one by eye, and every failure leaves with a ticket and an evidence bundle you can re-check — steps, HAR, console, clip — tied to what you actually saw.

MIT-licensed · runs on your machine · sample deck included

// where it fits

Automation checks what you told it to. A person notices what you didn’t.

Teasynaer is the human-in-the-loop half of testing — the cases you still verify by eye. It runs alongside your automated suite, not in place of it.

Pairs with automated runners — including the @restormel/testing-* family.

// what a pass looks like

Work the deck. Mark each case. File the fails.

Mark by key— P pass, F fail, S skip — or swipe the card left, right, or down.

Every fail leaves with proof— capture runs the whole time, so the ticket files with the steps you took, the failing request, the console error and a clip. No “oops, I didn’t hit record.”

Pick up where you left off— close the tab mid-run and the deck resumes exactly there.

A-H14/18

1 · Open /login

2 · Enter a known-bad password

expect→ rejected, no session

Fail · FSPass · P

← fail·pass →·skip ↓on fail → files TY-204 · bundle attached

// the run is only half of it

01 — Evidence

Already captured when it breaks

A rolling buffer records your steps, the network and the console for the whole run. A fail promotes it — HAR, console errors, screenshots, clip and environment file themselves onto the ticket.

inputs masked · auth headers redacted · before anything is stored

02 — Authoring

Cases you write. Evidence you can re-verify.

Author cases in Gherkin or steps-and-expected. The runner captures what happened during the pass; a fail promotes that buffer into a bundle you can inspect and attach to a tracker issue — no reconstructed server fiction.

recording → scenario drafting is on the roadmap, not a black-box generator

03 — Agent runs

Agents can rehearse; you attest

Steps can carry machine-addressable ⌖ targetsso an agent dry-runs them before you do — shrinking the deck to what still needs human eyes. Verdicts stay provisional until you confirm.

verdicts stay provisional · nothing is filed without you

// self-host in one file

Your data stays on your machine.

No SaaS, no seats, no telemetry. One container, one volume. Bring your own auth and you’re running.

# docker-compose.yml

services:

teasynaer:

image: git.allotmentology.tech/allotment-technology-ltd/teasynaer:latest

ports: ["8080:8080"]

volumes: [teasynaer-data:/data]

$ docker compose up → http://localhost:8080

// read before you run

Everything you need, without talking to anyone.

Five public docs cover the whole product — from first run to agent runs.

01Overviewwhat Teasynaer is — and what it isn'tdocs 02Getting startedfirst run to first filed fail in ten minutesdocs 03Running a passHome → Packages → Runner → summarydocs 04Writing cases & targetsGherkin vs steps-and-expected, Case Editordocs 05Importing tests & CIGherkin upload, TestRail, machine-import APIdocs 06Evidence & redactionwhat's captured, what's masked, where it livesdocs 07Issue trackers & notificationsGitHub, GitLab, Jira, Forgejo, Huly, webhooksdocs 08Reporting & exportstrends, compare, CI report, results exportdocs 09Self-hosting guidecompose file, volumes, backups, upgrades, reverse proxydocs 10Agent runsroadmap — not on main todaysoon