3 ms·
I like the ideas behind Deno, but I'm wondering if testing should be so included in the standard library, unless it is extremely flexible. Each team will have
by redleader55 5y ago
I like the ideas behind Deno, but I'm wondering if testing should be so included in the standard library, unless it is extremely flexible.
Each team will have different problems when it comes to scaling, running tests in parallel - sometimes on the same machine, sometimes on multiple machines, e2e tests vs unit-tests, etc. This looks like a problem you solve in a library, not something to add in the core.
- uhhhhhhhhhhhhhh 5y agoLegit concern but it's also possible they evolve a great general solution where everyone looks back and says "oh yeah that's what that api ought to be like"
- Soremwar 5y agoThere have been multiple test runners built on top of Deno's vanilla testing (through the JSON output feature), those may fit your use case better The current multi threaded and module isolated model however I think it's good for the great majority of projects, so I'm glad it's built in