Changes to how we handle fancy stacks:

pkg/unittest/lib/src/test_case.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.
 
 part of unittest;
 
 /**
  * Represents the state for an individual unit test.
  *
  * Create by calling [test] or [solo_test].
@@ skipping 23 matching lines @@
   String _message = '';
   /** Error or failure message. */
   String get message => _message;
 
   String _result;
   /**
    * One of [PASS], [FAIL], [ERROR], or [null] if the test hasn't run yet.
    */
   String get result => _result;
 
-  Trace _stackTrace;
+  var _stackTrace;
   /** Stack trace associated with this test, or [null] if it succeeded. */
-  Trace get stackTrace => _stackTrace;
+  get stackTrace => _stackTrace;

[nweiz, 2013/08/14 23:56:59]

I don't like making this dynamically-typed. This will make any code that
accesses it type check correctly but fail at runtime in one or the other
configuration.

It would be better to leave this typed as Trace, and then have a separate
stackTraceString field that's always a string representation of a stack trace,
regardless of whether fancy traces are enabled.

[gram, 2013/08/15 22:36:43]

Done.

 
   /** The group (or groups) under which this test is running. */
   final String currentGroup;
 
   DateTime _startTime;
   DateTime get startTime => _startTime;
 
   Duration _runningTime;
   Duration get runningTime => _runningTime;
 
@@ skipping 122 matching lines @@
   void error(String messageText, [stack]) {
     _complete(ERROR, messageText, stack);
   }
 
   void _markCallbackComplete() {
     if (--_callbackFunctionsOutstanding == 0 && !isComplete) {
       pass();
     }
   }
 }