pkg/unittest: fixed references to configuration implementations

pkg/unittest/lib/unittest.dart

-// Copyright (c) 2011, the Dart project authors.  Please see the AUTHORS file
+// 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.
  *
- * To import this library, use the pub package manager.
- * Create a pubspec.yaml file in your project and add
- * a dependency on unittest with the following lines:
- *     dependencies:
- *       unittest: any
- *
- * Then run 'pub install' from your project directory or using
- * the DartEditor.
- *
- * Please see [Pub Getting Started](http://pub.dartlang.org/doc)
- * for more details about the pub package manager.

[gram, 2013/03/05 18:55:33]

I think we may want to keep this. Siggy, what do you think?

[kevmoo-old, 2013/03/05 20:21:08]

Then should all pkg libraries have the pub instructions? Seems like something
that should be standardized and not special to unittest.

Even the description is a bit outdated since most folks will be using the Dart
editor to edit their pubspec file, right?

[Siggi Cherem (dart-lang), 2013/03/07 19:34:54]

So and so. Many of our users might not come to Dart and get started with pub
right away. It's hard to tell when they'll start using pub, but I believe that
for many developers 'unittest' is likely to be the first package from 'pkg'
they'll install with pub. That's why I lean towards making this package a bit
more informative about this than the rest.
We could rephrase things. It doesn't need to be too versbose, maybe just
combining the first and last sentence of this whole section might be enough:

"To import this library, install the [unittest
package](http://pub.dartlang.org/packages/unittest) via the pub package manager.
Please see [Pub Getting Started](http://pub.dartlang.org/doc) for more details."

I don't think we need to mention anything about how you edit your pubspec files,
let's just have the pub documentation deal with that.

[kevmoo-old, 2013/03/07 20:35:30]

Understood. On it.

- *
  * ##Concepts##
  *
- *  * Tests: Tests are specified via the top-level function [test], they can be
+ *  * __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 [Matcher]s
- *  * Configuration: The framework can be adapted by calling [configure] with a
- *    [Configuration].  Common configurations can be found in this package
- *    under: 'dom\_config.dart' (deprecated), 'html\_config.dart' (for running
- *    tests compiled to Javascript in a browser), and 'vm\_config.dart' (for
- *    running native Dart tests on the VM).
+ *  * __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 calling [configure] 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##
  *
  * A trivial test:
  *
  *     import 'package:unittest/unittest.dart';
  *     main() {
  *       test('this is a test', () {
  *         int x = 2 + 3;
  *         expect(x, equals(5));
@@ skipping 816 matching lines @@
 }
 
 /** Enable a test by ID. */
 void enableTest(int testId) => _setTestEnabledState(testId, true);
 
 /** Disable a test by ID. */
 void disableTest(int testId) => _setTestEnabledState(testId, false);
 
 /** Signature for a test function. */
 typedef dynamic TestFunction();