Add the ability to add to the tearDown for a running test

[nex3]

This is an idea that comes from scheduled_test. It makes it possible to create testing APIs that can clean up after themselves without the user having to explicitly pipe them to the tearDown. For example, a Sandbox class might tear down the sandbox directory; ScheduledProcess uses this to kill dangling processes.

[greglittlefield-wf]

Any updates on this issue? This feature would be nice to have.

[nex3]

None yet. If you want to contribute though, I'd gladly take a patch!

[greglittlefield-wf]

Cool, I'll look into it, then. Thanks!

[greglittlefield-wf]

It would be expected that any tearDowns added inside a test are run directly afterwards, before any group tearDowns, correct?

E.g., the following:

group('', () {
  tearDown(() => print('tearDown (group)');

  test('', {
    tearDown(() => print('tearDown (test)'));
    print('test');
  });
}

would output:

test
tearDown (test)
tearDown (group)

[nex3]

That's right. If multiple tear-downs are added within a test, they should also run in last-in-first-out order.