Add a test for timers in child isolates.

tests/html/async_test.dart

Index: tests/html/async_test.dart
diff --git a/tests/html/async_test.dart b/tests/html/async_test.dart
new file mode 100644
index 0000000000000000000000000000000000000000..95d61f5e418263041e05e1e6e559c89870d2c582
--- /dev/null
+++ b/tests/html/async_test.dart
@@ -0,0 +1,77 @@
+library async_test;
+
+import '../../pkg/unittest/lib/unittest.dart';
+import '../../pkg/unittest/lib/html_config.dart';
+
+import 'dart:async';
+import 'dart:isolate';
+import 'dart:html';
+
+oneshotTimerIsolate() {
+  port.receive((msg, replyTo) {
+    expect(msg, 'START');
+    new Timer(const Duration(milliseconds: 10), () {
+      replyTo.send('DONE');
+    });
+  });
+}
+
+periodicTimerIsolate() {
+  port.receive((msg, replyTo) {
+    expect(msg, 'START');
+    int counter = 0;
+    new Timer.periodic(const Duration(milliseconds: 10), (timer) {
+      if (counter == 3) {
+        counter = 1024;
+        timer.cancel();
+        // Wait some more time to be sure callback won't be invoked any
+        // more.
+        new Timer(const Duration(milliseconds: 30), () {
+          replyTo.send('DONE');
+        });
+      }
+      assert(counter < 3);
+      counter++;
+    });
+  });
+}
+
+cancellingIsolate() {
+  port.receive((msg, replyTo) {
+    expect(msg, 'START');
+    final oneshot = new Timer(const Duration(milliseconds: 30), () {
+      fail('Should never be invoked');

[vsm, 2013/03/29 14:37:39]

Will a 'fail' on a background isolate be caught be the test framework?  Might
need to send a message back.

[Anton Muhin, 2013/03/29 16:09:15]

That worked for me when I ran a single test from local server.

There are overall some issues with tests which I was going to discuss w/ Emily

Hopefully, even if fail is swollen, test should either fail or timeout anyway,
correct?

[vsm, 2013/03/29 17:34:36]

In this case, it looks like oneshot could fire/fail (silently in the background)
and periodic would still send DONE to the main thread.

If you're confident fail is doing the right thing and reporting properly, I'd
leave this as is.  I think you can test by setting oneshot to fire in 5 ms
instead of 30.  If it fails as expected, we're probably good.

If not, you could make shot (below) an int instead of a bool, and increment it
each time oneshot or periodic is fired.  And then, replace the replyTo message
with:
shot == 1 ? 'DONE' : 'FAIL'


On 2013/03/29 16:09:15, Anton Muhin wrote:

+    });
+    bool shot = false;
+    var periodic;
+    periodic = new Timer.periodic(const Duration(milliseconds: 10), (timer) {
+      expect(shot, isFalse);
+      shot = true;
+      expect(timer, same(periodic));
+      periodic.cancel();
+      oneshot.cancel();
+      // Wait some more time to be sure callbacks won't be invoked any
+      // more.
+      new Timer(const Duration(milliseconds: 50), () {
+        replyTo.send('DONE');
+      });
+    });
+  });
+}
+
+main() {
+  useHtmlConfiguration();
+
+  test('one shot timer in pure isolate', () {
+    expect(spawnFunction(oneshotTimerIsolate).call('START'),
+           completion('DONE'));
+  });
+  test('periodic timer in pure isolate', () {
+    expect(spawnFunction(oneshotTimerIsolate).call('START'),

[vsm, 2013/03/29 14:37:39]

oneshotTimerIsolate -> periodicTimerIsolate

[Anton Muhin, 2013/03/29 16:09:15]

Thanks!  Do'h.

+           completion('DONE'));
+  });
+  test('cancellation in pure isolate', () {
+    expect(spawnFunction(cancellingIsolate).call('START'),
+           completion('DONE'));
+  });
+}