angular-cn/packages/forms/test/BUILD.bazel

load("//tools:defaults.bzl", "jasmine_node_test", "karma_web_test_suite", "ts_library")

ts_library(
    name = "test_lib",
    testonly = True,
    srcs = glob(["**/*.ts"]),
    # Visible to //:saucelabs_unit_tests_poc target
    visibility = ["//:__pkg__"],
    deps = [
        "//packages/common",
        "//packages/core",
        "//packages/core/testing",
        "//packages/forms",
        "//packages/platform-browser",
        "//packages/platform-browser/testing",
        "//packages/private/testing",
        "@npm//rxjs",
    ],
)

jasmine_node_test(
    name = "test",
    bootstrap = ["//tools/testing:node_es5"],
    deps = [
        ":test_lib",
    ],
)

karma_web_test_suite(
    name = "test_web",
    deps = [
        ":test_lib",
    ],
)
build: ts_web_test & ts_web_test_suite deprecated in favor of karma_web_test & karma_web_test_suite (#33802) This is a breaking change in nodejs rules 0.40.0 as part of the API review & cleanup for the 1.0 release. Their APIs are identical as ts_web_test was just karma_web_test without the config_file attribute. PR Close #33802 2019-11-13 12:08:38 -05:00			`load("//tools:defaults.bzl", "jasmine_node_test", "karma_web_test_suite", "ts_library")`
build: add bazel test rules for remainder of packages (#21053) PR Close #21053 2017-12-17 18:10:54 -05:00
			`ts_library(`
			`name = "test_lib",`
test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags (#26471) We are close enough to blacklist a few test targets, rather than whitelist targets to run... Because bazel rules can be composed of other rules that don't inherit tags automatically, I had to explicitly mark all of our ts_library and ng_module targes with "ivy-local" and "ivy-jit" tags so that we can create a query that excludes all fixme- tagged targets even if those targets are composed of other targets that don't inherit this tag. This is the updated overview of ivy related bazel tags: - ivy-only: target that builds or runs only under ivy - fixme-ivy-jit: target that doesn't yet build or run under ivy with --compile=jit - fixme-ivy-local: target that doesn't yet build or run under ivy with --compile=local - no-ivy-jit: target that is not intended to build or run under ivy with --compile=jit - no-ivy-local: target that is not intended to build or run under ivy with --compile=local PR Close #26471 2018-10-16 02:24:22 -04:00			`testonly = True,`
build: add bazel test rules for remainder of packages (#21053) PR Close #21053 2017-12-17 18:10:54 -05:00			`srcs = glob(["*/.ts"]),`
ci: run acceptance tests on saucelabs with ivy (#34277) Currently we only run Saucelabs on PRs using the legacy View Engine build. Switching that build to Ivy is not trivial and there are various options: 1. Updating the R3 switches to use POST_R3 by default. At first glance, this doesn't look easy because the current ngtsc switch logic seems to be unidirectional (only PRE_R3 to POST_R3). 2. Updating the legacy setup to run with Ivy. This sounds like the easiest solution at first.. but it turns out to be way more complicated. Packages would need to be built with ngtsc using legacy tools (i.e. first building the compiler-cli; and then building packages) and View Engine only tests would need to be determined and filtered out. Basically it will result in re-auditing all test targets. This is contradictory to the fact that we have this information in Bazel already. 3. Creating a new job that runs tests on Saucelabs with Bazel. We specify fine-grained test targets that should run. This would be a good start (e.g. acceptance tests) and also would mean that we do not continue maintaining the legacy setup.. This commit implements the third option as it allows us to move forward with the general Bazel migration. We don't want to spend too much time on our legacy setup since it will be removed anyway in the future. PR Close #34277 2019-12-06 10:17:09 -05:00			`# Visible to //:saucelabs_unit_tests_poc target`
build(bazel): run a number of web tests with karma_web_test in saucelabs in CircleCI (#27721) PR Close #27721 2018-12-18 01:09:39 -05:00			`visibility = ["//:__pkg__"],`
build: add bazel test rules for remainder of packages (#21053) PR Close #21053 2017-12-17 18:10:54 -05:00			`deps = [`
refactor: Move `dom_adapter.ts` to `@angular/common` (#32154) This work is needed in preparation for turning tokens into tree-shakable injectables. PR Close #32154 2019-08-22 22:16:25 -04:00			`"//packages/common",`
build: add bazel test rules for remainder of packages (#21053) PR Close #21053 2017-12-17 18:10:54 -05:00			`"//packages/core",`
			`"//packages/core/testing",`
			`"//packages/forms",`
			`"//packages/platform-browser",`
			`"//packages/platform-browser/testing",`
test(ivy): run forms tests with ivy on ci (#26968) PR Close #26968 2018-11-06 17:02:22 -05:00			`"//packages/private/testing",`
build: rules_nodejs 0.26.0 & use @npm instead of @ngdeps now that downstream angular build uses angular bundles (#28871) PR Close #28871 2019-02-20 12:54:42 -05:00			`"@npm//rxjs",`
build: add bazel test rules for remainder of packages (#21053) PR Close #21053 2017-12-17 18:10:54 -05:00			`],`
			`)`

			`jasmine_node_test(`
			`name = "test",`
test: handle bootstrap templated_args in jasmine_node_test defaults.bzl (#34736) PR Close #34736 2020-01-08 02:56:49 -05:00			`bootstrap = ["//tools/testing:node_es5"],`
build: add bazel test rules for remainder of packages (#21053) PR Close #21053 2017-12-17 18:10:54 -05:00			`deps = [`
			`":test_lib",`
			`],`
			`)`

build: ts_web_test & ts_web_test_suite deprecated in favor of karma_web_test & karma_web_test_suite (#33802) This is a breaking change in nodejs rules 0.40.0 as part of the API review & cleanup for the 1.0 release. Their APIs are identical as ts_web_test was just karma_web_test without the config_file attribute. PR Close #33802 2019-11-13 12:08:38 -05:00			`karma_web_test_suite(`
build: add bazel test rules for remainder of packages (#21053) PR Close #21053 2017-12-17 18:10:54 -05:00			`name = "test_web",`
			`deps = [`
			`":test_lib",`
			`],`
			`)`