One-liners for unittest and matcher

pkg/unittest/lib/unittest.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.
 
 /**
- * A library for writing dart unit tests.
+ * Support for writing Dart unit tests.
  *
- * ## Installing ##
+ * For information on installing and importing this library, see the
+ * [unittest package on pub.dartlang.org]
+ * (http://pub.dartlang.org/packages/unittest).
  *
- * Use [pub][] to install this package. Add the following to your `pubspec.yaml`
- * file.
+ * **See also:**
+ * [Unit Testing with Dart]
+ * (http://www.dartlang.org/articles/dart-unit-tests/)
  *
- *     dependencies:
- *       unittest: any
- *
- * Then run `pub install`.
- *
- * For more information, see the
- * [unittest package on pub.dartlang.org][pkg].
- *
- * See the [Getting Started](http://pub.dartlang.org/doc)
- * guide for more details.
- *
- * ##Concepts##
+ * ##Concepts
  *
  *  * __Tests__: Tests are specified via the top-level function [test], they can be
  *    organized together using [group].
+ *
  *  * __Checks__: Test expectations can be specified via [expect]
+ *
  *  * __Matchers__: [expect] assertions are written declaratively using the
  *    [Matcher] class.
+ *
  *  * __Configuration__: The framework can be adapted by setting
  *    [unittestConfiguration] with a [Configuration]. See the other libraries
  *    in the `unittest` package for alternative implementations of
  *    [Configuration] including `compact_vm_config.dart`, `html_config.dart` and
  *    `html_enhanced_config.dart`.
  *
- * ##Examples##
+ * ##Examples
  *
  * A trivial test:
  *
  *     import 'package:unittest/unittest.dart';
  *     main() {
  *       test('this is a test', () {
  *         int x = 2 + 3;
  *         expect(x, equals(5));
  *       });
  *     }
@@ skipping 76 matching lines @@
  * returns false the test will still be considered incomplete.
  *
  * Test functions can return [Future]s, which provide another way of doing
  * asynchronous tests. The test framework will handle exceptions thrown by
  * the Future, and will advance to the next test when the Future is complete.
  * It is still important to use expectAsync/guardAsync with any parts of the
  * test that may be invoked from a top level context (for example, with
  * Timer.run()], as the Future exception handler may not capture exceptions
  * in such code.
  *
- * Note: due to some language limitations we have to use different functions
+ * Note: Due to some language limitations we have to use different functions
  * depending on the number of positional arguments of the callback. In the
  * future, we plan to expose a single `expectAsync` function that can be used
  * regardless of the number of positional arguments. This requires new langauge
  * features or fixes to the current spec (e.g. see
  * [Issue 2706](http://dartbug.com/2706)).
- *
- * [pub]: http://pub.dartlang.org
- * [pkg]: http://pub.dartlang.org/packages/unittest
  */
 library unittest;
 
 import 'dart:async';
 import 'dart:collection';
 import 'dart:isolate';
 import 'package:stack_trace/stack_trace.dart';
 
 import 'matcher.dart';
 export 'matcher.dart';
@@ skipping 735 matching lines @@
 
   if (!filterStacks) return trace;
 
   // Format the stack trace by removing everything above TestCase._runTest,
   // which is usually going to be irrelevant. Also fold together unittest and
   // core library calls so only the function the user called is visible.
   return new Trace(trace.frames.takeWhile((frame) {
     return frame.package != 'unittest' || frame.member != 'TestCase._runTest';
   })).terse.foldFrames((frame) => frame.package == 'unittest' || frame.isCore);
 }