George Kalpakas 19396769e2 ci: get rid of the `CI_CHROMEDRIVER_VERSION_ARG` env var (#35381) ... Previously, we needed to manually specify a ChromeDriver version to download on CI that would be compatible with the browser version provided by the docker image used to run the tests. This was kept in the `CI_CHROMEDRIVER_VERSION_ARG` environment variable. With recent commits, we use the browser provided by `puppeteer` and can determine the correct ChromeDriver version programmatically. Therefore, we no longer need the `CI_CHROMEDRIVER_VERSION_ARG` environment variable. NOTE: There is still one place (the `bazel-schematics` integration project) where a hard-coded ChromeDriver version is necessary. Since I am not sure what is the best way to refactor the tests to not rely on a hard-coded version, I left it as a TODO for a follow-up PR. PR Close #35381		2020-02-18 12:42:48 -08:00
..
.gitignore	test: ignore the generated `demo` folder in the `bazel` integration test (#29092)	2019-03-20 14:45:54 -04:00
package.json	test(bazel): Use local_repository to load Angular (#28061)	2019-01-11 16:19:59 -08:00
test.sh	ci: get rid of the `CI_CHROMEDRIVER_VERSION_ARG` env var (#35381)	2020-02-18 12:42:48 -08:00
yarn.lock	test: use puppeteer in integration tests and to download correct chromedriver (#35049)	2020-02-11 13:16:52 -08:00