Conversation

Notices

1. Embed this notice
   Nicholas C. Zakas (nzakas@fosstodon.org)'s status on Tuesday, 28-Nov-2023 05:52:21 JST Nicholas C. Zakas

   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?

   🤬

   • Embed this notice
     Sergey on FunctionalScript (functionalscript@techhub.social)'s status on Tuesday, 28-Nov-2023 05:52:20 JST Sergey on FunctionalScript

     in reply to

     @nzakas what's the reason to use platform-specific (Node) test framework?

   • Embed this notice
     Nicholas C. Zakas (nzakas@fosstodon.org)'s status on Tuesday, 28-Nov-2023 08:13:02 JST Nicholas C. Zakas

     in reply to

     • Sergey on FunctionalScript

     @functionalscript if I’m targeting the platform, then no extra dependency to manage.

   • Embed this notice
     Sergey on FunctionalScript (functionalscript@techhub.social)'s status on Tuesday, 28-Nov-2023 08:13:02 JST Sergey on FunctionalScript

     in reply to

     @nzakas removing additional [dev-]dependencies is a very good goal. I'm curious, if we can write testes the way, which can be used in any platform (Node, Deno, Bun, browsers...) and in any test-framework. Some kind of conventions.