ava

Shout out to AVA for running all tests async by default, which not only finds order-dependent issues, but also race condition and other timing related issues. https://github.com/avajs/ava

> In the popular jest test runner, each test file is executed in its own child process. Is that confirmed? I've been following this issue: https://github.com/jestjs/jest/issues/6957 And what Jest actually does is still kind of muddy. In contrast to that, other test runners like AVA have a clear description what happens when: https://github.com/avajs/ava/blob/main/docs/01-writing-tests...

You might want to give ava a spin: https://github.com/avajs/ava/ It has a TAP reporter, but more importantly, as opposed to the more popular solutions, like Jest, the way it achieves parallelism is explained in the docs and won't change anytime soon, thus preventing wonky, hard to debug errors which occur when this part is abstracted away.

I really enjoy Ava [1] or anything assert-tape-like [2]. "uvu" [3] is getting a lot of love lately, but it's very feature limited and much of it's touted advantages are at the detriment to feature set. [1] https://github.com/avajs/ava [2] https://github.com/substack/tape [3] https://github.com/lukeed/uvu Jest is great for front-end (or full stack integration) testing, but I feel it's specialized for that use-case and doesn't always play nice with backend/middle-tier testing needs.

I know a fella working on a Deno port of Ava (https://github.com/avajs/ava). When that and Koa are ported or compatible, I'll be giving Deno a legitimate go.

I actually started with Ava for a new project because it did a few things better than Jest. But ended up switching away because of this issue: https://github.com/avajs/ava/issues/2385 Basically, if an assertion fails in the middle of an individual test, most test runners stop executing that test. Ava (by design) continues on with the rest of that test. This makes it harder to debug issues. (This not be a problem for everyone. I'm only mentioning it because it was a deal-breaker for me and wish I knew that going in.)

I was surprised that every Jest+TypeScript guide says to use ts-jest. I already have my IDE, the TypeScript watcher, and ESLint parsing/compiling all the code! I don't want to add fourth one :-P I ended up just pointing Jest at my build output folder and that works. There are a couple minor annoyances but whatever. (I actually started with Ava because it more directly supports using the existing build output, but I ran into another issue and had to switch back to Jest: https://github.com/avajs/ava/issues/2385)

Ava (https://github.com/avajs/ava) gets too little love from the blogging machinery. It's a breeze to use with TS, faster than Jest (YMMV of course), and I love the snapshot output over any other snapshot producing unit test tool. Use with NYC for coverage is a breeze.

I use AVA[1] and c8[2] for coverage. It only works in node so I have to use JSDOM to mimic the browser environment. 1: https://github.com/avajs/ava 2: https://github.com/bcoe/c8

We ship Babel built in with the AVA[1] test runner and I can confirm `babel-require` is our bottleneck. [1] https://github.com/avajs/ava