Declare addTearDownLibrary.

[polina-c]

Prerequisite for flutter/flutter#138057.
TODO: add test coverage.

[natebosch]

Why do we need this over setUpAll and addTearDown?

[polina-c]

Why do we need this over setUpAll and addTearDown?

This method will tear down all tests in the library, not all tests in the group. I do not see other way to traverse to root group. Am i missing something?

[natebosch]

Why do we need this over setUpAll and addTearDown?

Because we need it to tear down all tests in the library, not all tests in the group. I do not see other way to traverse to root group. Am i missing something?

I thought the plan was to intercept the call to group and inject the setUpAll call?

If we want to avoid that because it's too brittle we can try something like this. I'd go with the name addTearDownSuite. @jakemac53 any concerns about such an API?

[natebosch]

Ah this isn't user facing either. Should be pretty safe then. Let's rename to "suite" and add a changelog entry.

Nope, we will need to change flutter_test/lib/src/test_compat.dart in order to use this API.
There are two ways: interception for group and others (internal) and added api (user facing).