We now have a mini_installer_tests target as of https://chromium-review.googlesource.com/c/chromium/src/+/969955

It's currently only hooked up on the Win 10 Fast Ring bot (https://ci.chromium.org/buildbot/chromium.fyi/Win%2010%20Fast%20Ring/ ; cf https://cs.chromium.org/search/?q=mini_installer_tests+file:buildbot&sq=package:chromium&type=cs). It's failing there with 

Set PYTHONPATH: E:\b\rr\tmph6_qjr\rw\scripts;E:\b\rr\tmph6_qjr\rw\site_config;E:\b\rr\tmph6_qjr\rw\third_party;E:\b\rr\tmph6_qjr\rw\third_party\buildbot_8_4p1;E:\b\rr\tmph6_qjr\rw\third_party\buildbot_slave_8_4;E:\b\rr\tmph6_qjr\rw\third_party\coverage-3.7.1;E:\b\rr\tmph6_qjr\rw\third_party\decorator_3_3_1;E:\b\rr\tmph6_qjr\rw\third_party\google_api_python_client;E:\b\rr\tmph6_qjr\rw\third_party\httplib2\python2;E:\b\rr\tmph6_qjr\rw\third_party\infra_libs;E:\b\rr\tmph6_qjr\rw\third_party\jinja2;E:\b\rr\tmph6_qjr\rw\third_party\markupsafe;E:\b\rr\tmph6_qjr\rw\third_party\oauth2client;E:\b\rr\tmph6_qjr\rw\third_party\pyasn1;E:\b\rr\tmph6_qjr\rw\third_party\pyasn1-modules;E:\b\rr\tmph6_qjr\rw\third_party\python-rsa;E:\b\rr\tmph6_qjr\rw\third_party\requests_2_10_0;E:\b\rr\tmph6_qjr\rw\third_party\setuptools-0.6c11;E:\b\rr\tmph6_qjr\rw\third_party\sqlalchemy_0_7_1;E:\b\rr\tmph6_qjr\rw\third_party\sqlalchemy_migrate_0_7_1;E:\b\rr\tmph6_qjr\rw\third_party\tempita_0_5;E:\b\rr\tmph6_qjr\rw\third_party\twisted_10_2;E:\b\rr\tmph6_qjr\rw\third_party\uritemplate;E:\b\rr\tmph6_qjr\rw\third_party\site-packages;E:\b\rr\tmph6_qjr\rw\scripts\tools;E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\python27.zip;E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\DLLs;E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib;E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib\plat-win;E:\b\depot_tools\win_tools-2_7_6_bin\python\bin\lib\lib-tk;E:\b\depot_tools\win_tools-2_7_6_bin\python\bin
[Running on builder: "Win 10 Fast Ring"]
Traceback (most recent call last):
  File "E:\b\rr\tmph6_qjr\rw\scripts\slave\runtest.py", line 1618, in <module>
    sys.exit(main())
  File "E:\b\rr\tmph6_qjr\rw\scripts\slave\runtest.py", line 1583, in main
    result = _MainWin(options, args, extra_env)
  File "E:\b\rr\tmph6_qjr\rw\scripts\slave\runtest.py", line 1165, in _MainWin
    raise chromium_utils.PathNotFound('Unable to find %s' % test_exe_path)
common.chromium_utils.PathNotFound: Unable to find E:\b\c\builder\Win_10_Fast_Ring\src\out\Release_x64\mini_installer_tests.exe
step returned non-zero exit code: 1


I also tried to use it in https://chromium-review.googlesource.com/#/c/986679/ thinking that this is how I'd run the installer tests on the bots (it isn't; calling steps.MiniInstallerTest() from the recipe is how I do this: https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/chromium_tests/chromium_win.py?type=cs&q=MiniInstallerTest&sq=package:chromium&l=45), and this target just comes back purple: https://ci.chromium.org/buildbot/chromium.clang/CrWinClang/3179 / https://chromium-swarm.appspot.com/task?id=3c8f66d03a55b410&refresh=10&show_raw=1

test_installer.py: error: unrecognized arguments: --test-launcher-summary-output=e:\b\swarm_slave\w\iobgp86y\output.json


It'd be cool if the target worked, and if we could then replace the current recipe-side execution of installer tests with the src-side configured one.