angular-cn/packages/compiler-cli/test/metadata/BUILD.bazel

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

ts_library(
    name = "test_lib",
    testonly = True,
    srcs = glob(["**/*.ts"]),
    deps = [
        "//packages:types",
        "//packages/compiler",
        "//packages/compiler-cli",
        "//packages/compiler-cli/test:test_utils",
        "//packages/core",
        "@npm//typescript",
    ],
)

jasmine_node_test(
    name = "test",
    bootstrap = ["//tools/testing:node_es5"],
    data = [
    ],
    deps = [
        ":test_lib",
        "//packages/core",
    ],
)
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")`
ci(compiler-cli): run compiler-cli tests in bazel (#22997) PR Close #22997 2018-03-21 17:22:06 -04: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,`
ci(compiler-cli): run compiler-cli tests in bazel (#22997) PR Close #22997 2018-03-21 17:22:06 -04:00			`srcs = glob(["*/.ts"]),`
			`deps = [`
			`"//packages:types",`
			`"//packages/compiler",`
			`"//packages/compiler-cli",`
fix(compiler-cli): Use typescript to resolve modules for metadata (#22856) The current module resolution simply attaches .ts to the import/export path, which does not work if the path is using Node / CommonJS behavior to resolve to an index.ts file. This patch uses typescript's module resolution logic, and will attempt to load the original typescript file if this resolution returns a .js or .d.ts file PR Close #22856 2018-07-06 20:02:08 -04:00			`"//packages/compiler-cli/test:test_utils",`
ci(compiler-cli): run compiler-cli tests in bazel (#22997) PR Close #22997 2018-03-21 17:22:06 -04:00			`"//packages/core",`
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//typescript",`
ci(compiler-cli): run compiler-cli tests in bazel (#22997) PR Close #22997 2018-03-21 17:22:06 -04:00			`],`
			`)`

			`jasmine_node_test(`
			`name = "test",`
test: handle bootstrap templated_args in jasmine_node_test defaults.bzl (#34589) PR Close #34589 2020-01-08 02:56:49 -05:00			`bootstrap = ["//tools/testing:node_es5"],`
ci(compiler-cli): run compiler-cli tests in bazel (#22997) PR Close #22997 2018-03-21 17:22:06 -04:00			`data = [`
			`],`
			`deps = [`
			`":test_lib",`
			`"//packages/core",`
			`],`
			`)`