Mark Wubben

Is that this one? https://github.com/avajs/ava/tree/a8981540100653d99d1fe9476737751eeae50b33/examples/typescript-context I think all those examples need updating to AVA 4. Will adjust this issue to reflect.

`cleanup` better communicates intended use. `.and.` feels overly verbose. Agreed that `afterEach` doesn't make sense for `.cleanupEach`.

> Hmm, wasn't .always supposed to serve this exact same purpose? To always run the clean up task, regardless of previous failure? That was our assumption, yes. The question though...

@catdad > While I don't disagree that it is a good idea to check that your environment is exactly as desired before a test, there has to be a stick...

@catdad It's only `--fail-fast` and crashes that prevent `always.after` from running. The benefit of `cleanup` over `after` is that it helps deal with those scenarios, too.

@sholladay I like your suggestion of having a `--no-cleanup` flag! @avajs/core?

>> I don't see the logic in skipping .afterEach when a test fails. > > If it would be totally up to me, I'd consider removing .always and making it...

> I know AVA likes to pave its own path, and to good effect. But I think Intern really gets this right. It makes strong guarantees that if a test...

I'd like to focus on outstanding Babel interoperability issues. But don't worry we won't shy away from making breaking changes when necessary, and we can support a deprecation path.

> Like doing a global `try ... catch` for the whole test file? Tests start running asynchronously so that won't work unfortunately.