I find the .only behavior of the Node.js built-in test runner maddening. Not only do I need to include --test-only on the CLI, but I also need to .only each "describe" and "it" all the way down to get a test to run?
@nzakas i ended up using process.exit to avoid having to pick a test framework, but would love to know which test framework to use these days for JS libs. https://github.com/pamelafox/ndjson-readablestream/blob/main/test.mjs
@pamelafox I’m still a big fan of Mocha for JS testing.
@nzakas what's the reason to use a platform-specific (Node) test framework?
@functionalscript if I’m targeting the platform, then no extra dependency to manage.
@nzakas removing additional [dev-]dependencies is a very good goal. I'm curious, if we can write tests the way, which can be used in any platform (Node, Deno, Bun, browsers...) and in any test-framework. Some kind of conventions.
@nzakas I am sure there is a technical performance related reason, but I absolutely agree it's a poor DX.