I agree that t.context.tmp should contain the full path of the temporary directory, not the relative. But, the setup and teardown functions should take care of setting all of this up. The setup and teardown functions might look like the beforeEach and afterEach in test/ln.js, for example. Then, in every test, we could just put test.beforeEach(setup) and test.afterEach(teardown). I don't know if ava has a way to do this globally for every test.

Another improvement might be using a dedicated temp directory module like tmp or tempy, though our solution should continue to work fine.

I don't know if ava has a way to do this globally for every test.

@freitagbr Huh? beforeEach() does run before every test, as-is. What did you mean?

I'll write up a PR in the next couple days.

Huh? beforeEach() does run before every test, as-is.

beforeEach() runs before every test in that file, but not for every file. Some test frameworks have a way to specify a beforeEach for every test in every file, but from reading the documentation, I don't think ava has a way to do this. But that's fine, it's not a big deal if each test file has beforeEach in it.

But that's fine, it's not a big deal if each test file has beforeEach in it.

Some test suites have different requirements from others. For example, some require a full copy of resources/ while others require an empty directory. So, for now it's nice that we have this flexibility.

Long-term, we should migrate most suites to the same beforeEach step (i.e. with a full copy of resources/). But even this doesn't make sense for tests like common.js, so we'll always want to specify per-suite.

Another thing (caught this in #874), we should robustly set process.env to its original value (resetting each property). This should happen in afterEach.always.