Add support for the new analyzer to the testing scripts

tools/test.dart

 #!/usr/bin/env dart
 // 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.
 
 /**
  * This file is the entrypoint of the dart test suite.  This suite is used
  * to test:
  *
  *     1. the dart vm
@@ skipping 126 matching lines @@
       maxBrowserProcesses = 1;
     }
 
     for (String key in selectors.keys) {
       if (key == 'co19') {
         testSuites.add(new Co19TestSuite(conf));
       } else if (conf['runtime'] == 'vm' && key == 'vm') {
         // vm tests contain both cc tests (added here) and dart tests (added in
         // [TEST_SUITE_DIRECTORIES]).
         testSuites.add(new VMTestSuite(conf));
+      } else if (conf['analyzer'] && key == 'dartc') {
+        testSuites.add(new SamplesDartcTestSuite(conf));
+        testSuites.add(new JUnitDartcTestSuite(conf));

[kustermann, 2013/03/12 17:55:23]

Why do we add these TestSuite's in case of the old analyzer but not the new one?

[ricow1, 2013/03/12 18:06:06]

we do add them for the new one, but we actually do not need it here, I will
change below instead (this was changed with Mads change to enable library
analyzing

       } else if (conf['compiler'] == 'dartc') {
         if (key == 'dartc') {
           testSuites.add(new SamplesDartcTestSuite(conf));
           testSuites.add(new JUnitDartcTestSuite(conf));
         }
         if (key == 'analyze_library') {
           testSuites.add(new AnalyzeLibraryTestSuite(conf));
         }
       }
     }
@@ skipping 20 matching lines @@
   new ProcessQueue(maxProcesses,
                    maxBrowserProcesses,
                    progressIndicator,
                    startTime,
                    printTiming,
                    testSuites,
                    allTestsFinished,
                    verbose,
                    listTests);
 }