[pigeon] Split CI and developer test scripts (#3076)

* Split into two files with no changes

* Adjust to fix compilation

* Duplicate run_tests to test with no changes

* Rework run_tests.dart

* Extract sharable code

* Make test.dart run every supported test

* Update all docs

* Update for changes in base PR

* Analysis, missed tests

* Move custom-test to heavy workload due to OOM

* Re-merge Cirrus configuration

Co-authored-by: Tarrin Neal <tarrinneal@gmail.com>

Author: stuartmorgan-g

.cirrus.yml

@@ -183,15 +183,6 @@ task:
       env:
         CIRRUS_CLONE_SUBMODULES: true
       script: ./script/tool_runner.sh update-excerpts --fail-on-change
-    - name: linux-custom_package_tests
-      env:
-        PATH: $PATH:/usr/local/bin
-        matrix:
-          CHANNEL: "master"
-          CHANNEL: "stable"
-      << : *INSTALL_CHROME_LINUX
-      local_tests_script:
-        - ./script/tool_runner.sh custom-test
     ### Web tasks ###
     - name: web-build_all_packages
       env:
@@ -237,6 +228,16 @@ task:
     cpu: 4
     memory: 16G
   matrix:
+    ### Platform-agnostic tasks ###
+    - name: linux-custom_package_tests
+      env:
+        PATH: $PATH:/usr/local/bin
+        matrix:
+          CHANNEL: "master"
+          CHANNEL: "stable"
+      << : *INSTALL_CHROME_LINUX
+      local_tests_script:
+        - ./script/tool_runner.sh custom-test
     ### Android tasks ###
     - name: android-platform_tests
       # Don't run full platform tests on both channels in pre-submit.

packages/pigeon/CONTRIBUTING.md

@@ -35,7 +35,7 @@ generators with that AST.
 ## Testing Overview
 
 Pigeon has 3 types of tests, you'll find them all in
-[run_tests.dart](./tool/run_tests.dart).
+[test.dart](./tool/test.dart).
 
 * Unit tests - These are the fastest tests that are just typical unit tests,
   they may be generating code and checking it against a regular expression to

packages/pigeon/platform_tests/README.md

@@ -1,11 +1,11 @@
 # Native Pigeon Tests
 
 This directory contains native test harnesses for native and end-to-end tests
-of Pigeon-generated code. The [test script](../tool/run_tests.dart) generates
+of Pigeon-generated code. The [test script](../tool/test.dart) generates
 native code from [pigeons/](../pigeons/) into the native test scaffolding, and
 then drives the tests there.
 
-To run these tests, use [`run_tests.dart`](../tool/run_tests.dart).
+To run these tests, use [`test.dart`](../tool/test.dart).
 
 Alternately, if you are running them directly (e.g., from within a platform
 IDE), you can use [`generate.dart`](../tool/generate.dart) to generate the

packages/pigeon/platform_tests/alternate_language_test_plugin/README.md

@@ -3,4 +3,4 @@
 Tests for languages not covered by `test_plugin`.
 See [the `platform_tests` README](../README.md) for details.
 
-To run these tests, use [`run_tests.dart`](../tool/run_tests.dart)
+To run these tests, use [`test.dart`](../tool/test.dart)

packages/pigeon/platform_tests/flutter_null_safe_unit_tests/lib/.gitignore

@@ -1,5 +1,5 @@
 # TODO(stuartmorgan) Remove this file when these are no longer generated;
-# see the TODO in _runFlutterUnitTests in run_tests.dart
+# see the TODO in _runFlutterUnitTests in test_suites.dart
 async_handlers.gen.dart
 host2flutter.gen.dart
 list.gen.dart