Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(232)

Unified Diff: lib/unittest.dart

Issue 850603002: Moving main library description to README.md (Closed) Base URL: https://github.com/dart-lang/unittest.git@master
Patch Set: cl nits Created 5 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « README.md ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: lib/unittest.dart
diff --git a/lib/unittest.dart b/lib/unittest.dart
index 72b5ea7deeab4d909dbddc5c3d51b2cfeb7d992f..791f0f553d5195ec1f6065fc913618955cdd2dc1 100644
--- a/lib/unittest.dart
+++ b/lib/unittest.dart
@@ -2,136 +2,6 @@
// 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.
-/// Support for writing Dart unit tests.
-///
-/// For information on installing and importing this library, see the
-/// [unittest package on pub.dartlang.org]
-/// (http://pub.dartlang.org/packages/unittest).
-///
-/// **See also:**
-/// [Unit Testing with Dart]
-/// (http://www.dartlang.org/articles/dart-unit-tests/)
-///
-/// ##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
-///
-/// A trivial test:
-///
-/// import 'package:unittest/unittest.dart';
-/// main() {
-/// test('this is a test', () {
-/// int x = 2 + 3;
-/// expect(x, equals(5));
-/// });
-/// }
-///
-/// Multiple tests:
-///
-/// import 'package:unittest/unittest.dart';
-/// main() {
-/// test('this is a test', () {
-/// int x = 2 + 3;
-/// expect(x, equals(5));
-/// });
-/// test('this is another test', () {
-/// int x = 2 + 3;
-/// expect(x, equals(5));
-/// });
-/// }
-///
-/// Multiple tests, grouped by category:
-///
-/// import 'package:unittest/unittest.dart';
-/// main() {
-/// group('group A', () {
-/// test('test A.1', () {
-/// int x = 2 + 3;
-/// expect(x, equals(5));
-/// });
-/// test('test A.2', () {
-/// int x = 2 + 3;
-/// expect(x, equals(5));
-/// });
-/// });
-/// group('group B', () {
-/// test('this B.1', () {
-/// int x = 2 + 3;
-/// expect(x, equals(5));
-/// });
-/// });
-/// }
-///
-/// Asynchronous tests: if callbacks expect between 0 and 6 positional
-/// arguments, [expectAsync] will wrap a function into a new callback and will
-/// not consider the test complete until that callback is run. A count argument
-/// can be provided to specify the number of times the callback should be called
-/// (the default is 1).
-///
-/// import 'dart:async';
-/// import 'package:unittest/unittest.dart';
-/// void main() {
-/// test('callback is executed once', () {
-/// // wrap the callback of an asynchronous call with [expectAsync] if
-/// // the callback takes 0 arguments...
-/// var timer = Timer.run(expectAsync(() {
-/// int x = 2 + 3;
-/// expect(x, equals(5));
-/// }));
-/// });
-///
-/// test('callback is executed twice', () {
-/// var callback = expectAsync(() {
-/// int x = 2 + 3;
-/// expect(x, equals(5));
-/// }, count: 2); // <-- we can indicate multiplicity to [expectAsync]
-/// Timer.run(callback);
-/// Timer.run(callback);
-/// });
-/// }
-///
-/// There may be times when the number of times a callback should be called is
-/// non-deterministic. In this case a dummy callback can be created with
-/// expectAsync((){}) and this can be called from the real callback when it is
-/// finally complete.
-///
-/// A variation on this is [expectAsyncUntil], which takes a callback as the
-/// first parameter and a predicate function as the second parameter. After each
-/// time the callback is called, the predicate function will be called. If it
-/// 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.
-///
-/// import 'dart:async';
-/// import 'package:unittest/unittest.dart';
-/// void main() {
-/// test('test that time has passed', () {
-/// var duration = const Duration(milliseconds: 200);
-/// var time = new DateTime.now();
-///
-/// return new Future.delayed(duration).then((_) {
-/// var delta = new DateTime.now().difference(time);
-///
-/// expect(delta, greaterThanOrEqualTo(duration));
-/// });
-/// });
-/// }
library unittest;
import 'dart:async';
« no previous file with comments | « README.md ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698