angular-cn/integration
JoostK fc6f48185c fix(ivy): ngcc - render decorators in UMD and CommonJS bundles correctly (#31614)
In #31426 a fix was implemented to render namespaced decorator imports
correctly, however it turns out that the fix only worked when decorator
information was extracted from static properties, not when using
`__decorate` calls.

This commit fixes the issue by creating the decorator metadata with the
full decorator expression, instead of only its name.

Closes #31394

PR Close #31614
2019-07-29 16:10:58 -07:00
..
bazel build: update to nodejs rules 0.34.0 and bazel 0.28.1 (#31824) 2019-07-26 15:01:25 -07:00
bazel-schematics fix(bazel): do not modify tsconfig.json (#30877) 2019-06-11 14:23:00 -07:00
cli-hello-world build: secure yarn lock files (#31640) 2019-07-29 16:10:23 -07:00
cli-hello-world-ivy-compat ci: update nodejs version to v10.16.0 (#31088) 2019-06-17 13:07:27 -07:00
cli-hello-world-ivy-minimal ci: update nodejs version to v10.16.0 (#31088) 2019-06-17 13:07:27 -07:00
dynamic-compiler ci: update nodejs version to v10.16.0 (#31088) 2019-06-17 13:07:27 -07:00
hello_world__closure ci: update nodejs version to v10.16.0 (#31088) 2019-06-17 13:07:27 -07:00
hello_world__systemjs_umd ci: update nodejs version to v10.16.0 (#31088) 2019-06-17 13:07:27 -07:00
i18n ci: update nodejs version to v10.16.0 (#31088) 2019-06-17 13:07:27 -07:00
injectable-def build: hide @angular/http for Angular v8 (#29550) 2019-04-02 10:55:31 -07:00
language_service_plugin fix(language-service): Remove 'any' in getQuickInfoAtPosition (#31014) 2019-06-14 10:46:16 -07:00
ng_elements ci: update nodejs version to v10.16.0 (#31088) 2019-06-17 13:07:27 -07:00
ng_update build: hide @angular/http for Angular v8 (#29550) 2019-04-02 10:55:31 -07:00
ngcc fix(ivy): ngcc - render decorators in UMD and CommonJS bundles correctly (#31614) 2019-07-29 16:10:58 -07:00
platform-server ci: update nodejs version to v10.16.0 (#31088) 2019-06-17 13:07:27 -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 feat(upgrade): provide unit test helpers for wiring up injectors (#16848) 2019-06-20 17:04:01 -07:00
typings_test_ts35 build: TypeScript 3.5 upgrade (#31615) 2019-07-25 17:05:23 -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): remove all old styling code prior to refactor (#31193) 2019-07-23 15:45:32 -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.