angular-docs-cn/packages/common/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/common/locales",
        "//packages/common/testing",
        "//packages/compiler",
        "//packages/core",
        "//packages/core/testing",
        "//packages/platform-browser",
        "//packages/platform-browser-dynamic",
        "//packages/platform-browser/testing",
        "//packages/private/testing",
    ],
)

jasmine_node_test(
    name = "test",
    bootstrap = ["angular/tools/testing/init_node_spec.js"],
    deps = [
        ":test_lib",
        "//tools/testing:node",
    ],
)

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 more packages (#21053) PR Close #21053 2017-12-16 23:08:49 -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 more packages (#21053) PR Close #21053 2017-12-16 23:08:49 -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 more packages (#21053) PR Close #21053 2017-12-16 23:08:49 -05:00			`deps = [`
			`"//packages/common",`
			`"//packages/common/locales",`
feat(common): add ability to retrieve the state from Location service (#30055) Previously there wasn't a way to retrieve `history.state` from the `Location` service. The only time the framework exposed this value was in navigation events. This meant if you weren't using the Angular router, there wasn't a way to get access to this `history.state` value other than going directly to the DOM. This PR adds an API to retrieve the value of `history.state`. This will be useful and needed to provide a backwards-compatible `Location` service that can emulate AngularJS's `$location` service since we will need to be able to read the state data in order to produce AngularJS location transition events. This feature will additionally be useful to any application that wants to access state data through Angular rather than going directly to the DOM APIs. PR Close #30055 2019-02-06 17:42:57 -05:00			`"//packages/common/testing",`
build: add bazel test rules for remainder of packages (#21053) PR Close #21053 2017-12-17 18:10:54 -05:00			`"//packages/compiler",`
build: add bazel test rules for more packages (#21053) PR Close #21053 2017-12-16 23:08:49 -05:00			`"//packages/core",`
			`"//packages/core/testing",`
			`"//packages/platform-browser",`
			`"//packages/platform-browser-dynamic",`
build: add bazel test rules for remainder of packages (#21053) PR Close #21053 2017-12-17 18:10:54 -05:00			`"//packages/platform-browser/testing",`
fix(ivy): process creation mode deeply before running update mode (#27744) Prior to this commit, we had two different modes for change detection execution for Ivy, depending on whether you called `bootstrap()` or `renderComponent()`. In the former case, we would complete creation mode for all components in the tree before beginning update mode for any component. In the latter case, we would run creation mode and update mode together for each component individually. Maintaining code to support these two different execution orders was unnecessarily complex, so this commit aligns the two bootstrapping mechanisms to execute in the same order. Now creation mode always runs for all components before update mode begins. This change also simplifies our rendering logic so that we use `LView` flags as the source of truth for rendering mode instead of `rf` function arguments. This fixed some related bugs (e.g. calling `ViewRef.detectChanges` synchronously after the view's creation would create view nodes twice, view queries would execute twice, etc). PR Close #27744 2018-12-18 19:58:51 -05:00			`"//packages/private/testing",`
build: add bazel test rules for more packages (#21053) PR Close #21053 2017-12-16 23:08:49 -05:00			`],`
			`)`

			`jasmine_node_test(`
			`name = "test",`
Revert "refactor: handle breaking changes in rules_nodejs 1.0.0 (#34589)" (#34730) This reverts commit 9bb349e1c8089ee29b82c7234a11ad4256f1d06f. PR Close #34730 2020-01-10 16:40:02 -05:00			`bootstrap = ["angular/tools/testing/init_node_spec.js"],`
build: add bazel test rules for more packages (#21053) PR Close #21053 2017-12-16 23:08:49 -05:00			`deps = [`
			`":test_lib",`
Revert "build: derive ts_library dep from jasmine_node_test boostrap label if it ends in `_es5` (#34589)" (#34730) This reverts commit 79a0d007b4e892dd988a8ef697e6d3436ea8391c. PR Close #34730 2020-01-10 16:39:37 -05:00			`"//tools/testing:node",`
build: add bazel test rules for more packages (#21053) PR Close #21053 2017-12-16 23:08:49 -05:00			`],`
			`)`

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 more packages (#21053) PR Close #21053 2017-12-16 23:08:49 -05:00			`name = "test_web",`
			`deps = [`
			`":test_lib",`
			`],`
			`)`