Kamino

Kamino was a no-code testing platform. The idea was simple: let anyone build and run end-to-end browser tests by drawing them, instead of writing Selenium by hand.

You build a User Path as a chain of steps, click this, type that, check that an element appeared, and each step targets a real element on the page. String them together and you have a repeatable test a non-developer can read and edit. Organise paths by project, environment and site, and the same suite runs across every version of a product.

What was in the box

A visual path editor. Steps as cards on a canvas: click, type, assert, with the target element and its parameters right there. No code to write, nothing to compile.

Visual regression. Screenshot comparison to catch what functional tests miss: the button that moved, the layout that quietly broke.

Interactive measurements over the rendered page, and a quick-fix flow for patching a broken selector without rebuilding the whole path.

Runners and visual reports so a test run reads like a report, not a wall of console output. A Jira integration to file what broke, and a training portal to get new testers going.

Why I built it

Test automation at scale is repetitive, brittle, and usually owned by the people least able to touch code. Kamino handed that power back: it made a test something you could see, build and fix without being an engineer. It runs on the same conviction as Synapse and, later, Mediagram, that the right editor turns a hard job into a visual one.