Add test_runner.dart to Dart version of test scripts. Include TestRunnerTest unit test.

tests/standalone/src/CrashTest.dart

Index: tests/standalone/src/CrashTest.dart
diff --git a/tests/standalone/src/CrashTest.dart b/tests/standalone/src/CrashTest.dart
new file mode 100644
index 0000000000000000000000000000000000000000..ac89618dd1d04ab15db09a8fe73a5ef22f0e6c72
--- /dev/null
+++ b/tests/standalone/src/CrashTest.dart
@@ -0,0 +1,23 @@
+// Copyright (c) 2011, the Dart project authors.  Please see the AUTHORS file

[Mads Ager (google), 2011/11/04 09:06:13]

I would prefer to find some other way of testing this. Adding a new test here
that relies on this crashing is going to make it annoying when that bug is
fixed.

Maybe we need to have a mode where we expose a couple of test methods. Including
one to crash the system. I would remove this test until we have that.

+// 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.
+
+
+// A test that crashes (for now).

[Søren Gjesse, 2011/11/04 09:05:34]

Does this crash due to a VM bug? We have a binary (process_test) which can be
made to crash reliabily, which you should probably use here. See the test
standalone/ProcessSegfaulttest.dart. And http://codereview.chromium.org/8365032/
for locating the binary.

+interface Link<T> factory LinkFactory {
+  Link.fromInt(int x);
+}
+
+class MyLink<T> implements Link<T> {
+}
+
+class LinkFactory {
+  factory Link.fromInt(int x) {
+    return new MyLink();
+  }
+}
+
+main() {
+  print("This goes to stdout.");
+  var a = new Link<int>.fromInt(2);
+}