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

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

ts_library(
    name = "test_lib",
    testonly = True,
    srcs = glob(
        ["**/*.ts"],
    ),
    visibility = [
        ":__subpackages__",
    ],
    deps = [
        "//packages:types",
        "//packages/compiler",
        "//packages/compiler-cli",
        "//packages/compiler-cli/src/ngtsc/file_system",
        "//packages/compiler-cli/test/compliance_old/mock_compile",
        "//packages/compiler/test:test_utils",
        "@npm//typescript",
    ],
)

jasmine_node_test(
    name = "compliance_old",
    bootstrap = ["//tools/testing:node_no_angular_es5"],
    data = [
        "//packages/compiler-cli/src/ngtsc/testing/fake_core:npm_package",
    ],
    shard_count = 2,
    tags = [
        "ivy-only",
    ],
    deps = [
        ":test_lib",
    ],
)
build(bazel): update to rules_typescript 0.17.0 & rules_nodejs 0.13.4 (#25920) PR Close #25920 2018-09-11 18:11:32 -07:00			`load("//tools:defaults.bzl", "jasmine_node_test", "ts_library")`
refactor(ivy): run the compiler compliance tests against ngtsc (#24862) This commit moves the compiler compliance tests into compiler-cli, and uses ngtsc to run them instead of the custom compilation pipeline used before. Testing against ngtsc allows for validation of the real compiler output. This commit also fixes a few small issues that prevented the tests from passing. PR Close #24862 2018-07-12 15:10:55 -07: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-15 23:24:22 -07:00			`testonly = True,`
refactor(ivy): run the compiler compliance tests against ngtsc (#24862) This commit moves the compiler compliance tests into compiler-cli, and uses ngtsc to run them instead of the custom compilation pipeline used before. Testing against ngtsc allows for validation of the real compiler output. This commit also fixes a few small issues that prevented the tests from passing. PR Close #24862 2018-07-12 15:10:55 -07:00			`srcs = glob(`
			`["*/.ts"],`
			`),`
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			`visibility = [`
			`":__subpackages__",`
			`],`
refactor(ivy): run the compiler compliance tests against ngtsc (#24862) This commit moves the compiler compliance tests into compiler-cli, and uses ngtsc to run them instead of the custom compilation pipeline used before. Testing against ngtsc allows for validation of the real compiler output. This commit also fixes a few small issues that prevented the tests from passing. PR Close #24862 2018-07-12 15:10:55 -07:00			`deps = [`
			`"//packages:types",`
			`"//packages/compiler",`
			`"//packages/compiler-cli",`
refactor(ivy): implement a virtual file-system layer in ngtsc + ngcc (#30921) To improve cross platform support, all file access (and path manipulation) is now done through a well known interface (`FileSystem`). For testing a number of `MockFileSystem` implementations are provided. These provide an in-memory file-system which emulates operating systems like OS/X, Unix and Windows. The current file system is always available via the static method, `FileSystem.getFileSystem()`. This is also used by a number of static methods on `AbsoluteFsPath` and `PathSegment`, to avoid having to pass `FileSystem` objects around all the time. The result of this is that one must be careful to ensure that the file-system has been initialized before using any of these static methods. To prevent this happening accidentally the current file system always starts out as an instance of `InvalidFileSystem`, which will throw an error if any of its methods are called. You can set the current file-system by calling `FileSystem.setFileSystem()`. During testing you can call the helper function `initMockFileSystem(os)` which takes a string name of the OS to emulate, and will also monkey-patch aspects of the TypeScript library to ensure that TS is also using the current file-system. Finally there is the `NgtscCompilerHost` to be used for any TypeScript compilation, which uses a given file-system. All tests that interact with the file-system should be tested against each of the mock file-systems. A series of helpers have been provided to support such tests: * `runInEachFileSystem()` - wrap your tests in this helper to run all the wrapped tests in each of the mock file-systems. * `addTestFilesToFileSystem()` - use this to add files and their contents to the mock file system for testing. * `loadTestFilesFromDisk()` - use this to load a mirror image of files on disk into the in-memory mock file-system. * `loadFakeCore()` - use this to load a fake version of `@angular/core` into the mock file-system. All ngcc and ngtsc source and tests now use this virtual file-system setup. PR Close #30921 2019-06-06 20:22:32 +01:00			`"//packages/compiler-cli/src/ngtsc/file_system",`
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",`
refactor(ivy): run the compiler compliance tests against ngtsc (#24862) This commit moves the compiler compliance tests into compiler-cli, and uses ngtsc to run them instead of the custom compilation pipeline used before. Testing against ngtsc allows for validation of the real compiler output. This commit also fixes a few small issues that prevented the tests from passing. PR Close #24862 2018-07-12 15:10:55 -07:00			`"//packages/compiler/test:test_utils",`
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 09:54:42 -08:00			`"@npm//typescript",`
refactor(ivy): run the compiler compliance tests against ngtsc (#24862) This commit moves the compiler compliance tests into compiler-cli, and uses ngtsc to run them instead of the custom compilation pipeline used before. Testing against ngtsc allows for validation of the real compiler output. This commit also fixes a few small issues that prevented the tests from passing. PR Close #24862 2018-07-12 15:10:55 -07:00			`],`
			`)`

			`jasmine_node_test(`
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			`name = "compliance_old",`
test: handle bootstrap templated_args in jasmine_node_test defaults.bzl (#34736) PR Close #34736 2020-01-07 23:56:49 -08:00			`bootstrap = ["//tools/testing:node_no_angular_es5"],`
refactor(ivy): run the compiler compliance tests against ngtsc (#24862) This commit moves the compiler compliance tests into compiler-cli, and uses ngtsc to run them instead of the custom compilation pipeline used before. Testing against ngtsc allows for validation of the real compiler output. This commit also fixes a few small issues that prevented the tests from passing. PR Close #24862 2018-07-12 15:10:55 -07:00			`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",`
refactor(ivy): run the compiler compliance tests against ngtsc (#24862) This commit moves the compiler compliance tests into compiler-cli, and uses ngtsc to run them instead of the custom compilation pipeline used before. Testing against ngtsc allows for validation of the real compiler output. This commit also fixes a few small issues that prevented the tests from passing. PR Close #24862 2018-07-12 15:10:55 -07:00			`],`
test(compiler-cli): improve test performance using shared source file cache (#38909) Some compiler tests take a long time to run, even using multiple executors. A profiling session revealed that most time is spent in parsing source files, especially the default libraries are expensive to parse. The default library files are constant across all tests, so this commit introduces a shared cache of parsed source files of the default libraries. This achieves a significant improvement for several targets on my machine: //packages/compiler-cli/test/compliance: from 23s to 5s. //packages/compiler-cli/test/ngtsc: from 115s to 11s. Note that the number of shards for the compliance tests has been halved, as the extra shards no longer provide any speedup. PR Close #38909 2020-09-13 20:31:33 +02:00			`shard_count = 2,`
refactor(ivy): run the compiler compliance tests against ngtsc (#24862) This commit moves the compiler compliance tests into compiler-cli, and uses ngtsc to run them instead of the custom compilation pipeline used before. Testing against ngtsc allows for validation of the real compiler output. This commit also fixes a few small issues that prevented the tests from passing. PR Close #24862 2018-07-12 15:10:55 -07:00			`tags = [`
			`"ivy-only",`
			`],`
			`deps = [`
			`":test_lib",`
			`],`
			`)`