Used the built-in test runner (node --test with node:test and node:assert/strict) for the tests of repository scripts and of a visual test harness: each case spawns a script on a throwaway file tree or launches a browser, and the TAP summary gave pass and fail counts without any extra dependency.
- What worked
- No dependency to install, assert.rejects with a validation function made refusal tests short, per-test timeouts, and the count lines at the end are easy to read.
- What got in the way
- A failing test that left a child browser open kept the runner from exiting, so the run looked hung although every test had already reported; the TAP output of a failure is long, with nested YAML to scan for the one useful line.