Post by @aral@mastodon.ar.al

🥳 Introducing Test Monkey

In my seemingly endless journey of yak shaving, I decided to port Tap Monkey¹ to node:test and make it into a test reporter.

https://codeberg.org/small-web/test-monkey#readme

> Displays test runner status using a static single-line spinner (hint: it’s a monkey) and only fills your screen with text on failures and with your coverage report.
>
> No dependencies.
>
> Did your tests pass? Excellent! Here, have a banana :) 🍌

Note: this is for when you’re running your unit tests manually and you want a calm, quiet, and monkey-filled experience. It’s not for CI.

Enjoy!

💕

¹ A tap formatter that’s also a monkey (see https://codeberg.org/small-tech/tap-monkey).

#NodeJS #testing #unitTests #nodeTest #Node24 #Node26 #test #dev #JavaScript #TestMonkey

#node26 #node24 #nodetest #testmonkey #unittests #testing #nodejs #test #javascript #dev

5 Replies

0 Boosts

Raul Portales

@Sh41@androiddev.social 3 min. ago

@aral Endless Yak shaving as a service: EYSasS

Aral Balkan

@aral@mastodon.ar.al 1 hr. ago

And speaking of shaving yaks (yes, even my yaks have yaks), I ended up going down a rabbit hole to try and create good quality terminal screencasts with small file size that can be embedded in READMEs and settled on a pipeline that uses VHS tapes to script the process, output lossless PNG frames, composite them with the cursor overlays, and join them together and convert them to WebP using ffmpeg.

So all I have to do to update the screencasts is to run:

screencasts/record

If you’re interested in doing something similar in your projects, I wrote up the process here:

https://codeberg.org/small-web/test-monkey/src/branch/main/screencasts#readme

#terminal #dev #screenCast #screenRecording #WebP #shell #VHS #ffmpeg #TestMonkey