ab27337612
This option is changed to true in Bazel 0.27 and exposes a possible regression in Bazel 0.27.0. Error observed is in npm_package target `//packages/common/locales:package`: ``` ERROR: /home/circleci/ng/packages/common/locales/BUILD.bazel:13:1: Assembling npm package packages/common/locales/package failed: No usable spawn strategy found for spawn with mnemonic SkylarkAction. Your --spawn_strategyor --strategy flags are probably too strict. Visit https://github.com/bazelbuild/bazel/issues/7480 for migration advises ``` Suspect is https://github.com/bazelbuild/rules_nodejs/blob/master/internal/npm_package/npm_package.bzl#L75-L82: ``` execution_requirements = { # Never schedule this action remotely because it's not computationally expensive. # It just copies files into a directory; it's not worth copying inputs and outputs to a remote worker. # Also don't run it in a sandbox, because it resolves an absolute path to the bazel-out directory # allowing the .pack and .publish runnables to work with no symlink_prefix # See https://github.com/bazelbuild/rules_nodejs/issues/187 "local": "1", }, ``` PR Close #31019 |
||
|---|---|---|
| .. | ||
| bazel | ||
| bazel-schematics | ||
| cli-hello-world | ||
| cli-hello-world-ivy-compat | ||
| cli-hello-world-ivy-minimal | ||
| dynamic-compiler | ||
| hello_world__closure | ||
| hello_world__systemjs_umd | ||
| i18n | ||
| injectable-def | ||
| language_service_plugin | ||
| ng_elements | ||
| ng_update | ||
| ngcc | ||
| platform-server | ||
| service-worker-schema | ||
| side-effects | ||
| terser | ||
| typings_test_ts34 | ||
| .gitignore | ||
| README.md | ||
| _payload-limits.json | ||
| get-sharded-tests.js | ||
| run_tests.sh | ||
README.md
Integration tests for Angular
This directory contains end-to-end tests for Angular. Each directory is a self-contained application that exactly mimics how a user might expect Angular to work, so they allow high-fidelity reproductions of real-world issues.
For this to work, we first build the Angular distribution just like we would publish it to npm, then install the distribution into each app.
To test Angular CLI applications, we use the integration test cli-hello-world.
When a significant change is released in the CLI, the application should be updated with ng update:
$ cd integration/cli-hello-world
$ yarn install
$ yarn ng update @angular/cli @angular-devkit/build-angular
# yarn build
# yarn test
# typescript version
Render3 tests
The directory cli-hello-world-ivy-compat contains a test for render3 used with the angular cli.
The cli-hello-world-ivy-minimal contains a minimal ivy app that is meant to mimic the bazel
equivalent in packages/core/test/bundling/hello_world, and should be kept similar.
Writing an integration test
The API for each test is:
- Each sub-directory here is an integration test
- Each test should have a
package.jsonfile - The test runner will run
yarnandyarn teston the package
This means that the test should be started by test script, like
"scripts": {"test": "runProgramA && assertResultIsGood"}
Note that the package.json file uses a special file://../../dist scheme
to reference the Angular packages, so that the locally-built Angular
is installed into the test app.
Also, beware of floating (non-locked) dependencies. If in doubt
you can install the package directly from file:../../node_modules.
Running integration tests
$ ./integration/run_tests.sh
The test runner will first re-build any stale npm packages, then cd into each
subdirectory to execute the test.