Vitest on Tokenise

Run your README's code blocks as Vitest tests so an agent can't leave the docs lying

Sat, 31 Oct 2026 16:04:00 +0000

An agent renames a function, updates every caller, fixes the tests, and ships a clean diff. The README still shows the old name. Nothing failed, because nothing reads the README except the next developer, who pastes the example, gets a compile error and loses ten minutes deciding whether to trust anything else on the page.

Move a JavaScript module to strict TypeScript one flag at a time, with the compiler and your tests as the gate

Fri, 30 Oct 2026 11:05:00 +0000

A 400-line JavaScript module has to become TypeScript, and the obvious plan is to rename every file to .ts, flip strict on and let an agent grind through the errors. That plan produces a diff nobody can review. Hundreds of errors arrive at once, the fastest way to silence them is any or a cast, and somewhere in the pile a “fix” quietly changes what the function returns.

Write the OpenAPI file first, then let the compiler and a short test catch every place the agent drifts from it

Fri, 30 Oct 2026 07:07:00 +0000

The ticket says the invoice response has a totalMinor field. The backend developer’s agent returns total, because that read more naturally to it. The frontend developer’s agent calls invoice.totalMinor, divides by 100 and renders NaN. Both pull requests are green. Each side’s tests were written by the side that made the mistake, so each side agreed with itself.

Let the tests run while the agent keeps typing: a background hook that interrupts only when something breaks

Wed, 28 Oct 2026 07:09:00 +0000

The agent edits a file, then edits another, then starts on a third. Somewhere in that sequence the first edit broke a test. Nobody finds out until the agent finishes its turn and runs the suite itself, if it remembers to. By then it has built two more changes on top of the broken one.

Make your agent earn the right to fix a flaky test: a shuffle-seed harness and a commit guard

Fri, 23 Oct 2026 07:09:00 +0000

A test fails in CI, passes on rerun, and somebody tells the agent to fix the flaky test. The agent reads the file, sees nothing wrong, and does the thing that makes the red go away: wraps it in a retry, adds a short sleep, or raises the timeout. CI goes green. The race is still there, now hidden behind a setting that nobody will look at again.

Pin a legacy function before an agent refactors it: record its outputs, then let StrykerJS grade the safety net

Tue, 20 Oct 2026 07:07:00 +0000

A function nobody wants to touch decides what customers pay, and an agent has just been asked to tidy it. The tests are thin, the original author left in 2021, and the diff that comes back reads fine. That’s the trap. A refactor that reads fine and changes a rounding rule is the most expensive kind, because nothing fails until an invoice does.