Execute onTestFinished handlers in the reverse order they are scheduled in

[nvie]

Clear and concise description of the problem

Currently, it looks like onTestFinished runs as a FIFO queue:

onTestFinished(() => console.log("foo"));
onTestFinished(() => console.log("bar"));

Output after test:

foo
bar

However, it seems to be more useful if those registrations are run in the reverse order they were scheduled in, so you can colocate setup and teardown code and never have to worry about the order of execution here:

// Suppose this code lives in a `getDb()` helper
const db = setupDb();
onTestFinished(() => db.teardown());

// And this code lives in a `getTable()` helper
const table = db.createTable();
onTestFinished(() => db.dropTable(table.name));

Right now, db.teardown() gets called before db.dropTable(), which causes an issue.

Suggested solution

If the order the teardown functions are run in is reversed, this class of problems will disappear.

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[sheremet-va]

I think they are actually called in parallel.

[sheremet-va]

Ideally, they should follow sequence.hooks option. So this is a bug at the very least.

[nvie]

Oh yeah, if sequence.hooks: "stack" could be used, that'd be great 👍