Mark Wubben

My impression is that somehow in worker threads `process.env` doesn't behave the same as in the main thread. This seems like unexpected behavior on Node.js part.

Internally AVA has quite a lot of data about the test execution that is not easily represented in TAP form. I think it'd be more powerful to convert that into...

I wasn't aware of ZAP. It's got the right motivation. But it's also ~4 years old, is there any ecosystem or tooling around it?

Could you elaborate on your CI use cases? Our reporting pipeline is in quite a state, and I'd want to make sure your contributions won't be in vain.

I wonder if there is a different approach we can take. The problem with reporter output is wanting it to be both human and machine readable. So even if AVA...

@codetheweb let's take it to https://github.com/avajs/ava/discussions/3004.

@jamiebuilds thank you for offering. I think at this stage, I'd rather we invest in the human readable reporter and making AVA more extensible through shared workers. Down the line...

We kick off the tests in source order though. The asynchronous ones will start to interleave but synchronous tests won't. And synchronous tests will block asynchronous ones that started earlier.

This is a neat approach to finding which tests in which order cause a failure: http://make.bettermistak.es/2016/03/05/rspecs-bisect/

@mighty-phoenix it is, though this behavior could be achieved using the [`sortTestFiles()` feature in 4.1.0](https://github.com/avajs/ava/releases/tag/v4.1.0). I'd still like to see it within AVA but the implementation has to be pretty...