> It is as good as unit testing, but reactive in the browser. I am confused about this because on the one hand, you seem to be hinting at my favorite, under-hy

> It is as good as unit testing, but reactive in the browser. I am confused about this because on the one hand, you seem to be hinting at my favorite, under-hyped aspect of testing, which is its use (via TDD) as a controlled-state print/debugger, but on the other you seem to be eliding the most popular--albeit, in my view, less important aspect (insofar as one aims for "working software over comprehensive documentation"[0])--the preservation of behavior across commits and into the future. What am I missing? Edit: re "reactive in the browser," that's how I run @benchristel/taste[1] 0. https://agilemanifesto.org/ https://agilemanifesto.org/ 1. https://github.com/benchristel/taste https://github.com/benchristel/taste