angular-cn/integration
Miško Hevery 09a2bb839f refactor(ivy): Intruduce LFrame to store global instruction information (#33178)
`LFrame` stores information specifice to the current `LView` As the code
enters and leaves `LView`s we use `enterView()` and `leaveView()`
respectively to build a a stack of `LFrame`s. This allows us to easily
restore the previous `LView` instruction state.

PR Close #33178
2019-10-24 14:42:15 -07:00
..
bazel test: update Angular CLI deps for integration tests (#32957) 2019-10-21 11:27:42 -04:00
bazel-schematics fix(bazel): Remove angular devkit and restore ngc postinstall (#32946) 2019-10-18 13:15:16 -04:00
cli-hello-world build: update CLI and related dependencies (#33382) 2019-10-24 14:12:30 -07:00
cli-hello-world-ivy-compat build: update CLI and related dependencies (#33382) 2019-10-24 14:12:30 -07:00
cli-hello-world-ivy-i18n build: update CLI and related dependencies (#33382) 2019-10-24 14:12:30 -07:00
cli-hello-world-ivy-minimal build: update CLI and related dependencies (#33382) 2019-10-24 14:12:30 -07:00
cli-hello-world-lazy build: update CLI and related dependencies (#33382) 2019-10-24 14:12:30 -07:00
cli-hello-world-lazy-rollup build: update CLI and related dependencies (#33382) 2019-10-24 14:12:30 -07:00
dynamic-compiler feat: typescript 3.6 support (#32946) 2019-10-18 13:15:16 -04:00
hello_world__closure feat: typescript 3.6 support (#32946) 2019-10-18 13:15:16 -04:00
hello_world__systemjs_umd feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
i18n feat: typescript 3.6 support (#32946) 2019-10-18 13:15:16 -04:00
injectable-def test: use @types/node compatible with TS 3.6 (#32946) 2019-10-18 13:15:17 -04:00
language_service_plugin feat: typescript 3.6 support (#32946) 2019-10-18 13:15:16 -04:00
ng_elements feat: typescript 3.6 support (#32946) 2019-10-18 13:15:16 -04:00
ng_update feat: typescript 3.6 support (#32946) 2019-10-18 13:15:16 -04:00
ng_update_migrations build: update CLI and related dependencies (#33382) 2019-10-24 14:12:30 -07:00
ngcc test: use @types/node compatible with TS 3.6 (#32946) 2019-10-18 13:15:17 -04:00
platform-server test: use @types/node compatible with TS 3.6 (#32946) 2019-10-18 13:15:17 -04:00
service-worker-schema test(service-worker): verify that `config/schema.json` is published to npm (#27859) 2019-03-05 16:48:26 -08:00
side-effects feat: typescript 3.6 support (#32946) 2019-10-18 13:15:16 -04:00
terser feat(compiler-cli): export tooling definitions (#29929) 2019-04-17 17:23:01 -07:00
typings_test_ts36 feat: typescript 3.6 support (#32946) 2019-10-18 13:15:16 -04:00
.gitignore test(ivy): i18n - add compile time translation to integration test (#32881) 2019-10-09 13:19:38 -07:00
README.md build: update render3 section of integration test readme (#28372) 2019-02-07 12:36:51 -08:00
_payload-limits.json refactor(ivy): Intruduce LFrame to store global instruction information (#33178) 2019-10-24 14:42:15 -07:00
get-sharded-tests.js build: shard integration tests on circleci (#27937) 2019-01-07 15:35:09 -08:00
run_tests.sh test: update Angular CLI deps for integration tests (#32957) 2019-10-21 11:27:42 -04:00

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.json file
  • The test runner will run yarn and yarn test on 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.