honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/upgrade/static/test/BUILD.bazel

37 lines
908 B
Python
Raw Normal View History

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", "karma_web_test_suite", "ts_library")
test: setup circular dependency tests for all entry points (#34774) Sets up circular dependency tests for all entry-points in the project (except for the ones part of a deprecated package). PR Close #34774
2020-01-14 09:31:13 -05:00
load("//tools/circular_dependency_test:index.bzl", "circular_dependency_test")
circular_dependency_test(
name = "circular_deps_test",
entry_point = "angular/packages/upgrade/static/index.js",
deps = ["//packages/upgrade/static"],
)
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,
refactor(upgrade): use Bazel packages to avoid symlinks in the source (#29466) Previously we had to share code between upgrade/dynamic and upgrade/static by symlinking the `src` folder, which allowed both packages to access the upgrade/common files. These symlinks are always problematic on Windows, where we had to run a script to re-link them, and restore them. This change uses Bazel packages to share the `upgrade/common` code, which avoids the need for symlinking the `src` folder. Also, the Windows specific scripts that fixup the symlinks have also been removed as there is no more need for them. PR Close #29466
2019-03-22 05:42:52 -04:00
srcs = glob([
"**/*.ts",
]),
build: add bazel test rules for remainder of packages (#21053) PR Close #21053
2017-12-17 18:10:54 -05:00
deps = [
"//packages/core",
"//packages/core/testing",
"//packages/platform-browser",
"//packages/platform-browser-dynamic",
"//packages/platform-browser/testing",
refactor(upgrade): use Bazel packages to avoid symlinks in the source (#29466) Previously we had to share code between upgrade/dynamic and upgrade/static by symlinking the `src` folder, which allowed both packages to access the upgrade/common files. These symlinks are always problematic on Windows, where we had to run a script to re-link them, and restore them. This change uses Bazel packages to share the `upgrade/common` code, which avoids the need for symlinking the `src` folder. Also, the Windows specific scripts that fixup the symlinks have also been removed as there is no more need for them. PR Close #29466
2019-03-22 05:42:52 -04:00
"//packages/upgrade/src/common",
"//packages/upgrade/src/common/test/helpers",
build: add bazel test rules for remainder of packages (#21053) PR Close #21053
2017-12-17 18:10:54 -05:00
"//packages/upgrade/static",
],
)
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(
refactor(upgrade): use Bazel packages to avoid symlinks in the source (#29466) Previously we had to share code between upgrade/dynamic and upgrade/static by symlinking the `src` folder, which allowed both packages to access the upgrade/common files. These symlinks are always problematic on Windows, where we had to run a script to re-link them, and restore them. This change uses Bazel packages to share the `upgrade/common` code, which avoids the need for symlinking the `src` folder. Also, the Windows specific scripts that fixup the symlinks have also been removed as there is no more need for them. PR Close #29466
2019-03-22 05:42:52 -04:00
name = "test",
build(bazel): re-enable packages/upgrade/test:test_web test with static_files in ts_web_test_suite (#24214) PR Close #24214
2018-05-31 02:49:37 -04:00
static_files = [
"//:angularjs_scripts",
build: add bazel test rules for remainder of packages (#21053) PR Close #21053
2017-12-17 18:10:54 -05:00
],
deps = [
":test_lib",
],
)