Looks interesting! What makes "a frame"? If text gets updated but cursor isn't set to the last row, how can it detect a new frame? Or does it flush changes on interval? We could probably use this to test summary reporter: github.com/vitest-dev/v...
So writing on multiple cursor positions on a single line causes multiple frames? We use synchronized updates to define what is a frame.
Building this integration has been amazing opportunity to dogfood all APIs we've added into @vitest.dev in past years. It's using features like new Reporter APIs, Vitest plugin hooks, browser commands, CDP, test tags and much more! Vitest is definitely one of the most extensible JS tools out there.
Which coverage metrics do you find the most useful? Which ones would be good defaults for typical users?
JS coverage ecosystem relies on defaults that were set ~12 years ago. Modern tools could break the cycle, but changing this old defaults is scary.
Get first access to our @vitest.dev plugin, which adds Chromatic’s visual testing and review to your browser tests. It’s built by @ariperkkio.dev, a Vitest core maintainer.
It’s free to use while in beta and requires no changes to your test files.
Read on for more info 🧵