Remove deprecated Expect from the libraries.

tests/standalone/debugger/debug_lib.dart

Index: tests/standalone/debugger/debug_lib.dart
diff --git a/tests/standalone/debugger/debug_lib.dart b/tests/standalone/debugger/debug_lib.dart
index 26f372508ee2d5b9a101cadc5a41b3f99ab6d6cd..76b6899774f685fa8b1694ddd4a637952127e93a 100644
--- a/tests/standalone/debugger/debug_lib.dart
+++ b/tests/standalone/debugger/debug_lib.dart
@@ -455,7 +455,7 @@ class Debugger {
       targetProcess.kill();
       print("Target process killed");
     }
-    Expect.isTrue(!errorsDetected);
+    if (errorsDetected) throw new Exception("Errors detected");

[Lasse Reichstein Nielsen, 2013/04/08 11:27:49]

Why use "Exception" and not "Error"?
Or perhaps just the string.

Exceptions are intended for libraries creating domain specific alternative
return values for exceptional cases.
I would expect a unit-test framework to have their own hierarchy of errors that
are neither programming Errors or Exception cases, but something the user code
doesn't even know about, and in the absence of a framework, just throw the
string.

[floitsch, 2013/04/08 12:06:47]

I wanted to use the Error class, but Error doesn't allow for a message. So I
switched to Exception instead.
I could fix the Error class to allow for a message.

[floitsch, 2013/04/08 16:06:59]

Done.

     exit(errors.length);
   }
 }
@@ -487,7 +487,7 @@ bool RunScript(List script) {
         print("Debug target process started");
         process.stdin.close();
         process.exitCode.then((int exitCode) {
-          Expect.equals(0, exitCode);
+          if (exitCode != 0) throw new Exception("bad exit code: $exitCode");
           print("Debug target process exited with exit code $exitCode");
         });
         var debugger =