Dartifying some IndexedDB APIs.

tests/html/utils.dart

 library TestUtils;
+import 'dart:async';
 import '../../pkg/unittest/lib/unittest.dart';
 
 /**
  * Verifies that [actual] has the same graph structure as [expected].
  * Detects cycles and DAG structure in Maps and Lists.
  */
 verifyGraph(expected, actual) {
   var eItems = [];
   var aItems = [];
 
@@ skipping 49 matching lines @@
         }
       }
       return;
     }
 
     expect(false, isTrue, reason: 'Unhandled type: $expected');
   }
 
   walk('', expected, actual);
 }
+
+void futureTest(spec, Future body()) {
+  test(spec, () {
+    expect(body(), completes);
+  });
+}
+
+/**
+ * Executes an array of test functions which return futures in parallel.
+ *
+ * This returns a future result of the last function.
+ */
+Future chainSteps(List<Function> steps) {
+  var future = steps[0]();
+  for (var step in steps.skip(1)) {
+    future = future.then(
+      (value) {
+        var result;
+        guardAsync(() {

[nweiz, 2013/02/05 02:03:19]

guardAsync shouldn't be necessary if you're using expect(..., completes).

[blois, 2013/02/05 03:02:42]

The error messages that I get from exceptions thrown from within the methods is
quite a bit better with guardAsync. Tests fail all the same, but the info is
better with guardAsync.

[nweiz, 2013/02/05 03:05:39]

How so? What's different about it?

[blois, 2013/02/06 23:34:13]

Resolution: issues unrelated to this code (unclosed DBs), fixed the core issue.

+          result = step(value);
+        });
+        return result;
+      });
+  }
+  return future;
+}