Testrunner for 3rd parties.

utils/testrunner/delete_task.dart

Index: utils/testrunner/delete_task.dart
===================================================================
--- utils/testrunner/delete_task.dart	(revision 0)
+++ utils/testrunner/delete_task.dart	(revision 0)
@@ -0,0 +1,20 @@
+// Copyright (c) 2012, 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 simeple pipeline task to delete a file.
+class DeleteTask extends PipelineTask {
+  final String _filenameTemplate;
+
+  DeleteTask(filenameTemplate) : _filenameTemplate = filenameTemplate;

[Siggi Cherem (dart-lang), 2012/08/30 16:46:40]

my understanding is that it is valid to say:
DeleteTask(this._filenameTemplate)

[gram, 2012/08/30 17:34:05]

It was decided some time back that private members should not be used in
constructors as they should not be exposed in Dart docs, and so the pattern I
use is the recommended way. At least this is true for named parameters; I'm not
100% sure about normal parameters but it seems the issue would still apply.

[Siggi Cherem (dart-lang), 2012/08/30 17:55:37]

good question - after talking with Bob, it seems that we do allow them and
currently prefer it.

+
+  void execute(Path testfile, List stdout, List stderr, bool verboseLogging,
+              Function exitHandler) {
+    var fname = expandMacros(_filenameTemplate, testfile);
+    deleteFile(fname);
+    if (verboseLogging) {
+      stdout.add('Removing $fname');
+    }
+    exitHandler(0);
+  }
+}