Added this to the M6 milestone.
Removed Priority-Unassigned label.
Added Priority-Medium label.

I'm not sure how best to deal with this. We could probably change the translator to generate each test into it's own file, but I'm not sure that's the right answer.

Are you suggesting that all of our tests should be like the language and co19 tests? Those are fine integration tests (although there are improvements I would like to see made to them), but I value being able to have unit tests as well. It really doesn't seem reasonable to not be able to run unit tests.

Perhaps we're just not running the tests the right way. Given a file that uses the unittest package to define multiple unit tests, how should we be running them?

Brian, it sounds like the right answer to me to generate many small files.

I strongly recommend against trying to dynamically split up tests. It doesn't scale, for example, dart2js will still take a long time compiling the test.

Removed this from the M6 milestone.
Added this to the M7 milestone.

M7 -> M8

Removed this from the M7 milestone.
Added this to the M8 milestone.

Removed this from the M8 milestone.
Added this to the M9 milestone.

Removed this from the M9 milestone.
Added this to the 1.1 milestone.

Removed this from the 1.1 milestone.
Added this to the 1.2 milestone.

Removed this from the 1.2 milestone.
Added this to the Later milestone.

I still don't know what to do about this. I really don't think it's reasonable to put every unit test in a separate file, and it doesn't look like other packages have their tests organized that way. Is there an approved way to structure unit tests written in Dart?

Set owner to @ricowind.
Removed Area-Analyzer label.
Added Area-Test label.

Perhaps you should look to dart2js for inspiration, rather than other packages. The analyzer and dart2js has a lot in common: large code base and complex tests.

In dart2js, we try to keep unit tests small. See tests/compiler/dart2js.

But I think you may have solved this by improving performance of the analyzer. I haven't seen the test time out in a while, and it seems to complete within reasonable time.

However, please keep in mind that our test framework is designed to run small tests, not big test suites like JUnit, so you generally don't want to have hundreds of tests per file. Also, keep in mind that when you look at what other packages do, you'll generally find a lot of examples of things that don't fit well with test.dart.

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

Removed Oldschool-Milestone-Later label.

Added AssumedStale label.