THE LAST
TEST

tlt · the proof is in the test

Say it in English. Run it. Send the URL.
tlt compiles plain-English test intent into a typed step list, runs it against a real browser, and publishes a shareable record. Customer asks "did you actually fix it?" — you send one link.

What it is

tlt is a single binary that does three things:

  1. Compile. Plain-English intent ("click the export button and assert the file downloads") becomes a typed step list, cached and signed.
  2. Run. The cached steps fire against a real browser via the pw-worker sidecar. PASS or FAIL with timings + screenshots.
  3. Publish. tlt publish r0042 uploads the run to the-last-test.com/r/<hash>. One stable URL per intent.

Customers open the URL on their phone and see the proof: intent text, every step with green check or red x, every screenshot, PASS or FAIL banner. No login. No install. No marketing. Just the record.

Recent records

No public records yet. The first tlt publish populates this list. Records land at /r/<hash>.

How to use it

$ tlt run --intent "after fix, the export button no longer hangs on >1000 rows" \
        --target https://customer.example.com/admin/export
tlt: r0142 PASS (4.2s)

$ tlt publish r0142
tlt: uploaded to https://the-last-test.com/r/9f8a72c4

Send the URL. They click it. They see the proof. You can't argue with right.

Download

Binary releases are on GitHub. Pinned by SHA. Download, unzip, run.