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

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

package(default_visibility = ["//visibility:public"])

ts_library(
    name = "test_lib",
    testonly = True,
    srcs = glob(
        ["**/*.ts"],
        exclude = [
            "**/*_node_only_spec.ts",
        ],
    ),
    # Visible to //:test_web_all target
    visibility = ["//:__pkg__"],
    deps = [
        "//packages/animations",
        "//packages/animations/browser",
        "//packages/animations/browser/testing",
        "//packages/common",
        "//packages/common/locales",
        "//packages/compiler",
        "//packages/compiler/testing",
        "//packages/core",
        "//packages/core/src/di/interface",
        "//packages/core/src/interface",
        "//packages/core/src/reflection",
        "//packages/core/src/util",
        "//packages/core/testing",
        "//packages/localize/init",
        "//packages/platform-browser",
        "//packages/platform-browser-dynamic",
        "//packages/platform-browser/animations",
        "//packages/platform-browser/testing",
        "//packages/private/testing",
        "//packages/router",
        "//packages/router/testing",
        "@npm//rxjs",
        "@npm//zone.js",
    ],
)

ts_library(
    name = "test_node_only_lib",
    testonly = True,
    srcs = glob(["**/*_node_only_spec.ts"]),
    deps = [
        ":test_lib",
        "//packages/compiler",
        "//packages/compiler/testing",
        "//packages/core",
        "//packages/core/src/compiler",
        "//packages/core/testing",
        "//packages/platform-server",
        "//packages/platform-server/testing",
        "//packages/private/testing",
    ],
)

jasmine_node_test(
    name = "test",
    bootstrap = ["angular/tools/testing/init_node_spec.js"],
    shard_count = 4,
    deps = [
        ":test_lib",
        ":test_node_only_lib",
        "//packages/platform-server",
        "//packages/platform-server/testing",
        "//tools/testing:node",
        "@npm//base64-js",
        "@npm//source-map",
        "@npm//zone.js",
    ],
)

ts_web_test_suite(
    name = "test_web",
    deps = [
        ":test_lib",
    ],
)
build(bazel): update to rules_typescript 0.17.0 & rules_nodejs 0.13.4 (#25920) PR Close #25920 2018-09-11 21:11:32 -04:00			`load("//tools:defaults.bzl", "jasmine_node_test", "ts_library", "ts_web_test_suite")`
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56:49 -05:00
style: enforce buildifier lint on CI (#28186) PR Close #28186 2019-01-16 04:19:01 -05:00			`package(default_visibility = ["//visibility:public"])`

build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56: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,`
feat(core): Moving Renderer3 into @angular/core (#20855) PR Close #20855 2017-12-01 17:23:03 -05:00			`srcs = glob(`
			`["*/.ts"],`
build(core): add bazel test targets for core (#21053) - Add tests target for `test`, `test_node_only` and `test_web` in `core` package. - Created a `_testing_init` pseudo package where bootstrap code for tests is kept. - Moved `source_map_util` from `test` to `testing` so to prevent circular dependency. - Removed `visibility:public` for testing `BUILD` packages. PR Close #21053 2017-12-16 14:35:47 -05:00			`exclude = [`
			`"*/_node_only_spec.ts",`
			`],`
feat(core): Moving Renderer3 into @angular/core (#20855) PR Close #20855 2017-12-01 17:23:03 -05:00			`),`
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			`# Visible to //:test_web_all target`
			`visibility = ["//:__pkg__"],`
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56:49 -05:00			`deps = [`
			`"//packages/animations",`
			`"//packages/animations/browser",`
			`"//packages/animations/browser/testing",`
			`"//packages/common",`
feat(ivy): use i18n locale data to determine the plural form of ICU expressions (#29249) Plural ICU expressions depend on the locale (different languages have different plural forms). Until now the locale was hard coded as `en-US`. For compatibility reasons, if you use ivy with AOT and bootstrap your app with `bootstrapModule` then the `LOCALE_ID` token will be set automatically for ivy, which is then used to get the correct plural form. If you use JIT, you need to define the `LOCALE_ID` provider on the module that you bootstrap. For `TestBed` you can use either `configureTestingModule` or `overrideProvider` to define that provider. If you don't use the compat mode and start your app with `renderComponent` you need to call `ɵsetLocaleId` manually to define the `LOCALE_ID` before bootstrap. We expect this to change once we start adding the new i18n APIs, so don't rely on this function (there's a reason why it's a private export). PR Close #29249 2019-05-17 10:13:31 -04:00			`"//packages/common/locales",`
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56:49 -05:00			`"//packages/compiler",`
			`"//packages/compiler/testing",`
			`"//packages/core",`
build: extract interface and util sub compilation from core (#28028) PR Close #28028 2019-01-09 16:49:16 -05:00			`"//packages/core/src/di/interface",`
			`"//packages/core/src/interface",`
refactor(ivy): refactor more files in DI to prepare it for bazel packages (#28098) PR Close #28098 2019-01-11 19:07:01 -05:00			`"//packages/core/src/reflection",`
build: extract interface and util sub compilation from core (#28028) PR Close #28028 2019-01-09 16:49:16 -05:00			`"//packages/core/src/util",`
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56:49 -05:00			`"//packages/core/testing",`
feat(ivy): i18n - reorganize entry-points for better reuse (#32488) This is a refactoring that moves the source code around to provide a better platform for adding the compile-time inlining. 1. Move the global side-effect import from the primary entry-point to a secondary entry-point @angular/localize/init. This has two benefits: first it allows the top level entry-point to contain tree-shakable shareable code; second it gives the side-effect import more of an "action" oriented name, which indicates that importing it does something tangible 2. Move all the source code into the top src folder, and import the localize related functions into the localize/init/index.ts entry-point. This allows the different parts of the package to share code without a proliferation of secondary entry-points (i.e. localize/utils). 3. Avoid publicly exporting any utilities at this time - the only public API at this point are the global `$localize` function and the two runtime helpers `loadTranslations()` and `clearTranslations()`. This does not mean that we will not expose additional helpers for 3rd party tooling in the future, but it avoid us preemptively exposing something that we might want to change in the near future. Notes: It is not possible to have the `$localize` code in the same Bazel package as the rest of the code. If we did this, then the bundled `@angular/localize/init` entry-point code contains all of the helper code, even though most of it is not used. Equally it is not possible to have the `$localize` types (i.e. `LocalizeFn` and `TranslateFn`) defined in the `@angular/localize/init` entry-point because these types are needed for the runtime code, which is inside the primary entry-point. Importing them from `@angular/localize/init` would run the side-effect. The solution is to have a Bazel sub-package at `//packages/localize/src/localize` which contains these types and the `$localize` function implementation. The primary `//packages/localize` entry-point imports the types without any side-effect. The secondary `//packages/localize/init` entry-point imports the `$localize` function and attaches it to the global scope as a side-effect, without bringing with it all the other utility functions. BREAKING CHANGES: The entry-points have changed: * To attach the `$localize` function to the global scope import from `@angular/localize/init`. Previously it was `@angular/localize`. * To access the `loadTranslations()` and `clearTranslations()` functions, import from `@angular/localize`. Previously it was `@angular/localize/run_time`. PR Close #32488 2019-08-10 07:51:30 -04:00			`"//packages/localize/init",`
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56:49 -05:00			`"//packages/platform-browser",`
			`"//packages/platform-browser-dynamic",`
			`"//packages/platform-browser/animations",`
			`"//packages/platform-browser/testing",`
refactor(core): remove withBody from public testing API (#25171) PR Close #25171 2018-07-27 16:49:22 -04:00			`"//packages/private/testing",`
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56:49 -05:00			`"//packages/router",`
			`"//packages/router/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",`
			`"@npm//zone.js",`
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56:49 -05:00			`],`
			`)`

build(core): add bazel test targets for core (#21053) - Add tests target for `test`, `test_node_only` and `test_web` in `core` package. - Created a `_testing_init` pseudo package where bootstrap code for tests is kept. - Moved `source_map_util` from `test` to `testing` so to prevent circular dependency. - Removed `visibility:public` for testing `BUILD` packages. PR Close #21053 2017-12-16 14:35:47 -05:00			`ts_library(`
			`name = "test_node_only_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(core): add bazel test targets for core (#21053) - Add tests target for `test`, `test_node_only` and `test_web` in `core` package. - Created a `_testing_init` pseudo package where bootstrap code for tests is kept. - Moved `source_map_util` from `test` to `testing` so to prevent circular dependency. - Removed `visibility:public` for testing `BUILD` packages. PR Close #21053 2017-12-16 14:35:47 -05:00			`srcs = glob(["*/_node_only_spec.ts"]),`
			`deps = [`
			`":test_lib",`
			`"//packages/compiler",`
			`"//packages/compiler/testing",`
			`"//packages/core",`
test(core): update JIT source mapping tests for ivy (#28055) There are some differences in how ivy maps template source compared to View Engine. In this commit we recreate the View Engine tests for ivy. PR Close #28055 2019-02-08 17:10:20 -05:00			`"//packages/core/src/compiler",`
build(core): add bazel test targets for core (#21053) - Add tests target for `test`, `test_node_only` and `test_web` in `core` package. - Created a `_testing_init` pseudo package where bootstrap code for tests is kept. - Moved `source_map_util` from `test` to `testing` so to prevent circular dependency. - Removed `visibility:public` for testing `BUILD` packages. PR Close #21053 2017-12-16 14:35:47 -05:00			`"//packages/core/testing",`
			`"//packages/platform-server",`
			`"//packages/platform-server/testing",`
fix(ivy): Enable AoT tests to run on CI; disable failing tests (#26975) PR Close #26975 2018-11-05 23:31:54 -05:00			`"//packages/private/testing",`
build(core): add bazel test targets for core (#21053) - Add tests target for `test`, `test_node_only` and `test_web` in `core` package. - Created a `_testing_init` pseudo package where bootstrap code for tests is kept. - Moved `source_map_util` from `test` to `testing` so to prevent circular dependency. - Removed `visibility:public` for testing `BUILD` packages. PR Close #21053 2017-12-16 14:35:47 -05:00			`],`
			`)`

build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56:49 -05:00			`jasmine_node_test(`
			`name = "test",`
build: Remove angular_src nested workspace (#21096) PR Close #21096 2017-12-19 18:03:29 -05:00			`bootstrap = ["angular/tools/testing/init_node_spec.js"],`
build: enable shard_count for some jasmine tests that have many specs (#31009) This partitions the spects across multiple processes so they run in parallel. PR Close #31009 2019-03-08 19:35:36 -05:00			`shard_count = 4,`
build(core): add bazel test targets for core (#21053) - Add tests target for `test`, `test_node_only` and `test_web` in `core` package. - Created a `_testing_init` pseudo package where bootstrap code for tests is kept. - Moved `source_map_util` from `test` to `testing` so to prevent circular dependency. - Removed `visibility:public` for testing `BUILD` packages. PR Close #21053 2017-12-16 14:35:47 -05:00			`deps = [`
			`":test_lib",`
			`":test_node_only_lib",`
			`"//packages/platform-server",`
			`"//packages/platform-server/testing",`
build: move _testing_init into tools; limit web_test concurrency (#21053) PR Close #21053 2017-12-18 18:37:05 -05:00			`"//tools/testing:node",`
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//base64-js",`
			`"@npm//source-map",`
			`"@npm//zone.js",`
build(core): add bazel test targets for core (#21053) - Add tests target for `test`, `test_node_only` and `test_web` in `core` package. - Created a `_testing_init` pseudo package where bootstrap code for tests is kept. - Moved `source_map_util` from `test` to `testing` so to prevent circular dependency. - Removed `visibility:public` for testing `BUILD` packages. PR Close #21053 2017-12-16 14:35:47 -05:00			`],`
			`)`

test: switch to ts_web_test_suite (#23859) Unit tests now run on Firefox too PR Close #23859 2018-05-11 12:43:06 -04:00			`ts_web_test_suite(`
build(core): add bazel test targets for core (#21053) - Add tests target for `test`, `test_node_only` and `test_web` in `core` package. - Created a `_testing_init` pseudo package where bootstrap code for tests is kept. - Moved `source_map_util` from `test` to `testing` so to prevent circular dependency. - Removed `visibility:public` for testing `BUILD` packages. PR Close #21053 2017-12-16 14:35:47 -05:00			`name = "test_web",`
build: upgrade bazel rules to latest (#20768) Add enough BUILD files to make it possible to `bazel build packages/core/test` Also re-format BUILD.bazel files with Buildifier. Add a CI lint check that they stay formatted. PR Close #20768 2017-12-06 09:56:49 -05:00			`deps = [`
			`":test_lib",`
			`],`
			`)`