Add flag to disable capturing stack traces.

pkg/scheduled_test/lib/scheduled_test.dart

Index: pkg/scheduled_test/lib/scheduled_test.dart
diff --git a/pkg/scheduled_test/lib/scheduled_test.dart b/pkg/scheduled_test/lib/scheduled_test.dart
index b46dc45006e26c2d35d5c2c92c1179424abbbed7..2e0dbd99854760d7de7ee4018dc0d3496c691e8d 100644
--- a/pkg/scheduled_test/lib/scheduled_test.dart
+++ b/pkg/scheduled_test/lib/scheduled_test.dart
@@ -201,6 +201,14 @@ Schedule _currentSchedule;
 /// `unittest.setUp`.
 Function _setUpFn;
 
+/// If `true`, then new [Task]s will capture the current stack trace before
+/// running. This can be set to `false` to speed up running tests since
+/// capturing stack traces is currently quite slow. Even when set to `false`,
+/// stack traces from *thrown* exceptions will be caught. This only disables
+/// the eager collection of stack traces *before* an error occurs. Defaults to
+/// `true`.
+bool captureStackTraces = true;

[nweiz, 2013/04/09 21:25:58]

I'd rather see this on the Schedule class. That's where other scheduled test
configuration has gone.

[Bob Nystrom, 2013/04/10 21:52:00]

Done.

+
 /// Creates a new test case with the given description and body. This has the
 /// same semantics as [unittest.test].
 void test(String description, void body()) =>