Would the tests be able to specify flags such as --test-launcher-timeout=90000, --test-launcher-batch-limit=25, or --test-launcher-jobs=1?

We also pass some flags conditionally based on build type, e.g. 

      if (!is_cast_desktop_build) {
        args += [ "--use-gpu-in-tests" ]
      }

which would probably require creating many BUILDFLAGs

Do you know if we can also pass the gtest filters this way?

Not that we necessarily have to solve all of the uses of flags in Comment 1 the same way.

One advantage of the current system is that all the flags for a given test (foo_unittests) can be found in the foo_unittests_filter variable.

Also of note is that building the "cast_test_lists" target with ninja will generate the out_*/release/tests/run_test_list.txt file, which lists the full command line for every unittest. It might be worthwhile to create a lightweight version of this target that generates the list without needing to build all the unittest executables

-test-launcher-foo flags are not important for running locally, so they can be specified in filters. I believe chromium uses recipes for such flags?

Ideally we should not have to worry about using gpu or not. It should be transparent to the code/test by using whatever GL driver (mesa or real) is present. We can look at such flags on a case-by-cases basis and fix the code/test if necessary.

The problem with cast_test_lists is that:
1. Very few people know about it
2. Developers need to find the file; open it; copy-paste flags. This bug is about removing this hassle.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot