angular/integration/forms/BUILD.bazel

load("//integration:index.bzl", "ng_integration_test")

ng_integration_test(
    name = "test",
    setup_chromium = True,
    track_payload_size = "forms",
)
build: setup test targets for integration tests with new rule (#44238) Sets up the test targets for integration tests with the new rule. The targets will match the configuration of the previous integration test setup (through the dictionary in a `bzl` file). Note: We already add `setup_chromium` based on whether Chromium tests run as part of this integration test. In a follow-up commit we can then remove puppeteer and rely on the Bazel-managed version of Chromium. PR Close #44238 2021-11-20 16:15:22 +00:00			`load("//integration:index.bzl", "ng_integration_test")`

			`ng_integration_test(`
			`name = "test",`
			`setup_chromium = True,`
build: fix integration test size trackings not running after recent refactoring (#44430) Fixes that the integration test size trackings stopped working due to the recent refactorings (switch to the rule from `@angular/dev-infra-private`). The size-tracking does not integrate very-well into Bazel and needs a better solution in the future, allowing for RBE and Windows support, but currently with the new rule/setup/structure the tracking does not validate sizes because: * The `dist/.js` argument to the tracking script got expanded and messed up the indices. It should be passed as a literal. This now surfaced because the new rule runs commands in a shell. The name for the size goldens were not computed properly because they were based on `ctx.attr.name`, but given the new structure, the test targets are always named `test`. PR Close #44430 2021-12-09 21:45:07 +00:00			`track_payload_size = "forms",`
build: setup test targets for integration tests with new rule (#44238) Sets up the test targets for integration tests with the new rule. The targets will match the configuration of the previous integration test setup (through the dictionary in a `bzl` file). Note: We already add `setup_chromium` based on whether Chromium tests run as part of this integration test. In a follow-up commit we can then remove puppeteer and rely on the Bazel-managed version of Chromium. PR Close #44238 2021-11-20 16:15:22 +00:00			`)`