Post

Frequently work with teams who are uncomfortable changing software they own because of low test confidence and / or coverage. Generated this small tool for .NET projects (it's written in TypeScript, don't loose your minds) which acts as a meta-harness, instruments a codebase with Coverlet + Stryker

and delegates out to your Agent CLI of choice to raise outside-in component / developer test statement coverage up to your target.

It has canned prompts that do their best to mimic your existing test style and only isolate out of process dependencies, with a deterministic shell that measures coverage and mutation test rules, letting the agents only do the test uplift, rather than an agent judging the work.

These tests, while stylistically "component tests" probably act more like snapshot testing - the idea is that they lock in what the program currently does, using the big statistical dice roll machine to do the thing it's good at (fuzzy matching and replication).

There's a strong focus on purely outside-in tests, rather than unit testing, because anything more granular would lock you into your specific implementation and make your code harder to change.

If we're now in a world where you want to do risky changes with agents or big traditional refactors, starting from a place of confidence is important, give it a go. github.com/davidwhitney...