angular-docs-cn/integration
Alex Rickabaugh ec4381dd40 feat: make the Ivy compiler the default for ngc (#32219)
This commit switches the default value of the enableIvy flag to true.
Applications that run ngc will now by default receive an Ivy build!

This does not affect the way Bazel builds in the Angular repo work, since
those are still switched based on the value of the --define=compile flag.
Additionally, projects using @angular/bazel still use View Engine builds
by default.

Since most of the Angular repo tests are still written against View Engine
(particularly because we still publish VE packages to NPM), this switch
also requires lots of `enableIvy: false` flags in tsconfigs throughout the
repo.

Congrats to the team for reaching this milestone!

PR Close #32219
2019-08-20 16:41:08 -07:00
..
bazel feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
bazel-schematics feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
cli-hello-world feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
cli-hello-world-ivy-compat build: update tslint to version ~5.18.0 (#31879) 2019-08-09 10:47:43 -07:00
cli-hello-world-ivy-minimal build: update tslint to version ~5.18.0 (#31879) 2019-08-09 10:47:43 -07:00
dynamic-compiler feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
hello_world__closure feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07: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: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
injectable-def feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
language_service_plugin test(language-service): Remove test for external template (#32017) 2019-08-14 11:57:48 -07:00
ng_elements feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07:00
ng_update build: hide @angular/http for Angular v8 (#29550) 2019-04-02 10:55:31 -07:00
ngcc build(zone.js): update zone.js to 0.10.2 (#31975) 2019-08-16 09:56:41 -07:00
platform-server feat: make the Ivy compiler the default for ngc (#32219) 2019-08-20 16:41:08 -07: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 refactor(core): cleanup code with side-effects which was preventing tree-shaking (#30580) 2019-06-03 09:01:51 -07:00
terser feat(compiler-cli): export tooling definitions (#29929) 2019-04-17 17:23:01 -07:00
typings_test_ts34 test: fix outDir in TS integration tests (#29284) 2019-07-31 11:40:27 -07:00
typings_test_ts35 test: fix outDir in TS integration tests (#29284) 2019-07-31 11:40:27 -07:00
.gitignore ci: Add back the CLI integration test with pinning (#21555) 2018-01-25 22:18:55 -08: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): simplify `walkTNodeTree` method for readability (#31065) 2019-08-19 10:12:38 -07:00
get-sharded-tests.js build: shard integration tests on circleci (#27937) 2019-01-07 15:35:09 -08:00
run_tests.sh ci: do not install firebase-tools without cache (#28615) 2019-02-08 10:23:19 -08: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.