iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
angular-docs-cn/packages/compiler-cli/test/compliance_old/prelink/BUILD.bazel

39 lines
986 B
Python
Raw Normal View History

test(compiler-cli): run compliance tests for two compilation modes … (#38938) To verify the correctness of the linker output, we leverage the existing compliance tests. The plan is to test the linker by running all compliance tests using a full round trip of pre-linking and subsequently post-linking, where the generated code should be identical to a full AOT compile. This commit adds an additional Bazel target that runs the compliance tests in partial mode. Follow-up work is required to implement the logic for running the linker round trip. PR Close #38938
2020-09-22 15:42:33 +01:00
load("//tools:defaults.bzl", "jasmine_node_test", "ts_library")
ts_library(
name = "prelink_bootstrap",
testonly = True,
srcs = ["bootstrap.ts"],
deps = [
"//packages:types",
test(compiler-cli): run the linker transform in the compliance test's prelink target (#39518) In PR #38938 an additional Bazel target was introduced for the compliance tests, as preparation to run the compliance tests in partial compilation mode and then apply the linker transform. The linker plugin itself was not available at the time but has since been implemented, so this commit updates the prelink target of the compliance tests to apply the linker transform using the Babel plugin. Actually emitting partial compilations to be transformed will be done in follow-up work. PR Close #39518
2020-10-30 23:04:09 +01:00
"//packages/compiler-cli/linker/babel",
refactor(compiler-cli): move legacy compliance tests to new folder (#39617) This commit renames the original `compliance` test directory to `compliance_old`. Eventually this directory will be deleted once all the tests have been migrated to the new test case based compliance tests. PR Close #39617
2020-11-11 15:29:42 +00:00
"//packages/compiler-cli/test/compliance_old/mock_compile",
test(compiler-cli): run the linker transform in the compliance test's prelink target (#39518) In PR #38938 an additional Bazel target was introduced for the compliance tests, as preparation to run the compliance tests in partial compilation mode and then apply the linker transform. The linker plugin itself was not available at the time but has since been implemented, so this commit updates the prelink target of the compliance tests to apply the linker transform using the Babel plugin. Actually emitting partial compilations to be transformed will be done in follow-up work. PR Close #39518
2020-10-30 23:04:09 +01:00
"@npm//@babel/core",
"@npm//@babel/generator",
"@npm//@babel/template",
"@npm//@babel/types",
"@npm//@types/babel__core",
"@npm//@types/babel__generator",
"@npm//@types/babel__template",
test(compiler-cli): skip compliance tests that target ES5 for partial compilation tests (#39707) The linker does not currently support outputting ES5 syntax, so any compliance tests that request ES5 output cannot be run in partial compilation mode. This commit marks these tests as pending. PR Close #39707
2020-11-16 18:12:31 +01:00
"@npm//typescript",
test(compiler-cli): run compliance tests for two compilation modes … (#38938) To verify the correctness of the linker output, we leverage the existing compliance tests. The plan is to test the linker by running all compliance tests using a full round trip of pre-linking and subsequently post-linking, where the generated code should be identical to a full AOT compile. This commit adds an additional Bazel target that runs the compliance tests in partial mode. Follow-up work is required to implement the logic for running the linker round trip. PR Close #38938
2020-09-22 15:42:33 +01:00
],
)
jasmine_node_test(
name = "prelink",
bootstrap = [
"//tools/testing:node_no_angular_es5",
":prelink_bootstrap_es5",
],
data = [
test(compiler-cli): move testing utils to separate package (#39594) ngtsc has a robust suite of testing utilities, designed for in-memory testing of a TypeScript compiler. Previously these utilities lived in the `test` directory for the compiler-cli package. This commit moves those utilities to an `ngtsc/testing` package, enabling them to be depended on separately and opening the door for using them from the upcoming language server testing infrastructure. As part of this refactoring, the `fake_core` package (a lightweight API replacement for @angular/core) is expanded to include functionality needed for Language Service test use cases. PR Close #39594
2020-11-04 12:27:19 -08:00
"//packages/compiler-cli/src/ngtsc/testing/fake_core:npm_package",
test(compiler-cli): run compliance tests for two compilation modes … (#38938) To verify the correctness of the linker output, we leverage the existing compliance tests. The plan is to test the linker by running all compliance tests using a full round trip of pre-linking and subsequently post-linking, where the generated code should be identical to a full AOT compile. This commit adds an additional Bazel target that runs the compliance tests in partial mode. Follow-up work is required to implement the logic for running the linker round trip. PR Close #38938
2020-09-22 15:42:33 +01:00
],
shard_count = 4,
tags = [
"ivy-only",
],
deps = [
refactor(compiler-cli): move legacy compliance tests to new folder (#39617) This commit renames the original `compliance` test directory to `compliance_old`. Eventually this directory will be deleted once all the tests have been migrated to the new test case based compliance tests. PR Close #39617
2020-11-11 15:29:42 +00:00
"//packages/compiler-cli/test/compliance_old:test_lib",
test(compiler-cli): run compliance tests for two compilation modes … (#38938) To verify the correctness of the linker output, we leverage the existing compliance tests. The plan is to test the linker by running all compliance tests using a full round trip of pre-linking and subsequently post-linking, where the generated code should be identical to a full AOT compile. This commit adds an additional Bazel target that runs the compliance tests in partial mode. Follow-up work is required to implement the logic for running the linker round trip. PR Close #38938
2020-09-22 15:42:33 +01:00
],
)
Reference in New Issue Copy Permalink