Make Completers asynchronous.

pkg/scheduled_test/test/substitute_future_test.dart

 // Copyright (c) 2013, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 library substitute_future_test;
 
 import 'dart:async';
 
 import 'package:scheduled_test/src/substitute_future.dart';
 import 'package:unittest/unittest.dart';
@@ skipping 130 matching lines @@
       completer1.completeError(1);
       completer2.completeError(2);
       completer3.completeError(3);
     });
   });
 
   test('substituting after a future has completed is an error', () {
     var completer = new Completer();
     var future = new SubstituteFuture(completer.future);
     completer.complete('success');
-    expect(() => future.substitute(new Future.value()),
-        throwsStateError);
+    future.then(expectAsync1((_) {
+      expect(() => future.substitute(new Future.value()),
+          throwsStateError);
+    }));

[nweiz, 2013/05/07 00:11:52]

[expectAsync*] is usually less expressive than [expect]/[completes]. In this
case, you could write:

    expect(future.then((_) => future.substitute(new Future.value())),
        throwsStateError);

since [throwsA] is Future-aware by default.

Also, add a comment here explaining why this needs to be async.

[floitsch, 2013/05/13 11:19:25]

done in CL 15128002.

   });
 }