Cairn Tools
Graph-driven testing for complex codebases.
Cairn Tools takes a graph-driven approach to software testing — modelling how the pieces of a codebase connect so you can see how a change ripples outward, rather than running the same flat test suite and hoping nothing downstream broke. The idea is to make testing understand structure, not just execute assertions.
The problem it’s aiming at
Most test suites are a flat list: hundreds or thousands of checks that all run the same way regardless of what you actually changed. That has two failure modes every working developer knows. Either the suite is fast and shallow, so a change quietly breaks something three modules away that nothing covered — or it’s exhaustive and slow, so you run the whole thing on every commit and wait, and eventually people stop waiting.
A graph-driven model treats the codebase as what it really is: a web of dependencies. If you know that module A is imported by B, which is called by the checkout flow in C, then a change to A tells you exactly what’s downstream and worth exercising. That’s the promise here — testing that follows the blast radius of a change instead of ignoring it.
Where this helps most
The bigger and more interconnected a codebase gets, the more valuable this kind of structural awareness becomes. On a small project you can hold the dependency map in your head; on a large one, nobody can, and “what might this break?” becomes a genuinely hard question that reviewers answer by guessing. A tool that can trace the ripple is aimed squarely at teams past that threshold — the ones where a one-line change has, at least once, taken down something nobody expected.
The honest status
Cairn is early. The public site is still light on detail, and there’s no mature feature set to evaluate today — so treat this as a “worth watching” entry rather than a product to adopt right now. We won’t dress up a pre-launch page as more than it is. What’s here is a clearly stated direction (graph-driven testing) and a real developer pain it’s pointed at; whether it delivers is something to check back on as it opens up.
Why it’s here
Cairn comes from the same studio as FindMeeting — Code Shock — and it targets a problem the team feels directly: knowing what a change might break before it ships. If graph-based testing is your kind of problem, keep an eye on it. In the meantime, the rest of the network is further along, and FindMeeting itself is free and ready today.
New here? FindMeeting is the free group scheduler from the same team — or read the guides and see the rest of the network.