Allow tests to be selected by name.

bin/unittest.dart

 // Copyright (c) 2015, 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.
 
 library unittest.unittest;
 
 import 'dart:async';
 import 'dart:io';
 import 'dart:isolate';
 
 import 'package:args/args.dart';
 import 'package:stack_trace/stack_trace.dart';
 
 import 'package:unittest/src/backend/test_platform.dart';
 import 'package:unittest/src/runner/reporter/compact.dart';
 import 'package:unittest/src/runner/load_exception.dart';
 import 'package:unittest/src/runner/loader.dart';
 import 'package:unittest/src/util/exit_codes.dart' as exit_codes;
 import 'package:unittest/src/util/io.dart';
 import 'package:unittest/src/utils.dart';
 
 /// The argument parser used to parse the executable arguments.
 final _parser = new ArgParser(allowTrailingOptions: true);
 
 void main(List<String> args) {
   _parser.addFlag("help", abbr: "h", negatable: false,
       help: "Shows this usage information.");
   _parser.addOption("package-root", hide: true);
+  _parser.addOption("name",
+      abbr: 'n',
+      help: 'A substring of the name of the test to run.\n'
+          'Regular expression syntax is supported.');

[kevmoo, 2015/03/28 22:02:26]

In theory I like regex support, but since we allow tests to have any name – even
regex "special" chars, I'd almost want regexp parsing to be opt-in (or at least
opt-out).

Makes it a lot easier to safely tool, etc

[nweiz, 2015/03/30 19:45:41]

I personally hate it when I have to switch up my command-line flags to enable
regexps in a tool. I think it's very unlikely to cause problems. The most common
regexp-active character is ".", which will still match a literal ".", and even
if the test name does contain something like "+" or "()", mostly this flag will
just be passed a couple adjacent words so that won't come up in practice.
I don't know what this means.

[kevmoo, 2015/03/30 19:51:49]

I'm fine if plain text is opt in. But we should absolutely support plain text.
Safely tool: I can wrap the command line API with a dumb script that just sends
an identical String match without having to worry about making them regex
friendly

[nweiz, 2015/03/30 20:08:09]

Done.

   _parser.addOption("platform",
       abbr: 'p',
       help: 'The platform(s) on which to run the tests.',
       allowed: TestPlatform.all.map((platform) => platform.identifier).toList(),
       defaultsTo: 'vm',
       allowMultiple: true);
   _parser.addFlag("color", defaultsTo: null,
       help: 'Whether to use terminal colors.\n(auto-detected by default)');
 
   var options;
@@ skipping 26 matching lines @@
       }
       paths = ["test"];
     }
 
     return Future.wait(paths.map((path) {
       if (new Directory(path).existsSync()) return loader.loadDir(path);
       if (new File(path).existsSync()) return loader.loadFile(path);
       throw new LoadException(path, 'Does not exist.');
     }));
   }).then((suites) {
+    suites = flatten(suites);
+
+    if (options["name"] != null) {
+      var expression = new RegExp(options["name"]);
+      suites = suites.map((suite) {
+        return suite.change(
+            tests: suite.tests.where((test) => expression.hasMatch(test.name)));
+      }).toList();
+
+      if (suites.every((suite) => suite.tests.isEmpty)) {
+        stderr.writeln('No tests match "${options["name"]}".');
+        exitCode = exit_codes.data;
+        return null;
+      }
+    }
+
     var reporter = new CompactReporter(flatten(suites), color: color);
     return reporter.run().then((success) {
       exitCode = success ? 0 : 1;
     }).whenComplete(() => reporter.close());
   }).catchError((error, stackTrace) {
     if (error is LoadException) {
       stderr.writeln(error.toString(color: color));
 
       // Only print stack traces for load errors that come from the user's 
       if (error.innerError is! IOException &&
@@ skipping 37 matching lines @@
     output = stderr;
   }
 
   output.write("""$message
 
 Usage: pub run unittest:unittest [files or directories...]
 
 ${_parser.usage}
 """);
 }