Closes #621

Closes #578

Closes #579

Closes #555

Closes #554

We're using a feature that was introduced in
1.6.0 (Disconnector.disconnect's return value).

Closes #556

Closes #539

This prints debugging information only if the test actually fails.

This also adds a (private) AsyncMatcher class that makes it easier to
define asynchronous matchers, and generally improves the formatting of
those matchers.

This reverts commit 35f9d92a.

This doesn't fully support the JSON reporter yet.

See #50

See #109
Closes #93

This worked with the old expectAsync(), but was broken when the new
functions were introduced. It was causing an analysis error in the
tests.

This adds `spawnHybridUri()` and `spawnHybridCode()` methods that spawn
VM isolates even when called from the browser. It still needs some
additional work to close the isolates when the test ends by default.

See #109

BUG=
R=nweiz@google.com

Review URL: https://codereview.chromium.org//2557183002 .

Dartium wasn't emitting any standard IO on Windows, which caused us to
stall out waiting for the Observatory URL in debug mode.

See dart-lang/sdk#28034
Closes #425

Closes #503

Review URL: https://codereview.chromium.org//2526223002 .

Fixes #436.

R=nweiz@google.com

Review URL: https://codereview.chromium.org//2515303002 .

Also update the pubspec and changelog.

If a web test emitted any kind of message after the browser manager was
closed, the debugging timer would reset and cause the VM not to exit for
an extra three seconds.

Make test iframes visible when debugging.

Closes #429

Closes #485

R=nweiz@google.com
BUG=

Review URL: https://codereview.chromium.org//2392743005 .

Don't capture stack traces by default.

Stack traces are now only captured for the JSON reporter. Capturing
traces was slow enough to be a serious problem for test suites with many
tests.

Closes #457