The compact reporter isn't really compact if you have errors, info messages, or skips in your test run. It's particularly difficult if there are multiple failures, or if you're using CI and the failures don't happen to be the very last tests that are run.

I have started work on addressing this: master...dnfield:test_reporter but want to solicit feedback. Some things I can think of that we want to acheive:

1. Any invocation of the test package use the new reporter (whether for packags/flutter, packages/flutter_tools, or wherever else in our repo). My WIP change is only handling flutter test at the moment.
2. Right now I'm just wrapping the json reporter. We could write our own reporter, but ultimately I'd like to see us able to use the data from our test runs in a more structured manner for analytics, which will probably require wrapping the JSON reporter anyway.

/cc @jonahwilliams