4 ms·
I guess the argument is that testing is very often another piece of the "developer experience" of a project, akin to linting or compilation. It makes some amoun
by ketzo 6y ago
I guess the argument is that testing is very often another piece of the "developer experience" of a project, akin to linting or compilation. It makes some amount of sense to me, although I see where you're coming from.
- pseudoramble 6y agoRight. I'm genuinely not trying to make a judgement on the choice - it's just not the choice I'm used to seeing, including in JS environments. So it seems like there must be some reasoning behind it. I suppose that's true! Practically speaking, it would be nice to have one testing framework to learn and use over-and-over again, but that's also kinda counter to what I'm used to in the JS world.