angular-cn/integration
Paul Gschwendtner 2ba799ddc7 fix(bazel): do not typecheck core schematic files (#29876)
Currently for Angular Bazel projects, NGC needs to be run in the
"postinstall" NPM script in order to generate required summary files.

We need to update the postinstall `tsconfig` to not check/re-build the
`@angular/core` schematic code which has transitive dependencies
which are only available inside of a CLI project. As this is not guaranteed
to be the case with Angular Bazel projects, we need to make sure that
we don't check/re-build these files.

PR Close #29876
2019-04-18 18:22:09 -07:00
..
bazel fix(bazel): do not typecheck core schematic files (#29876) 2019-04-18 18:22:09 -07:00
bazel-schematics build(bazel): Bump CLI and @angular-devkit/* to v8 beta 15 (#29966) 2019-04-18 13:53:33 -07:00
cli-hello-world feat(bazel): update the build to use the new architect api (#29720) 2019-04-08 09:47:34 -07:00
cli-hello-world-ivy-compat feat(bazel): update the build to use the new architect api (#29720) 2019-04-08 09:47:34 -07:00
cli-hello-world-ivy-minimal feat(bazel): update the build to use the new architect api (#29720) 2019-04-08 09:47:34 -07:00
dynamic-compiler build: update to TypeScript 3.4 (#29372) 2019-04-10 12:12:16 -07:00
hello_world__closure ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494) 2019-02-01 20:22:03 -05:00
hello_world__systemjs_umd ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494) 2019-02-01 20:22:03 -05:00
i18n ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494) 2019-02-01 20:22:03 -05:00
injectable-def build: hide @angular/http for Angular v8 (#29550) 2019-04-02 10:55:31 -07:00
language_service_plugin test(language-service): Improve integration test (#28168) 2019-01-17 14:11:28 -08:00
ng_elements ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494) 2019-02-01 20:22:03 -05:00
ng_update build: hide @angular/http for Angular v8 (#29550) 2019-04-02 10:55:31 -07:00
ngcc refactor(ivy): use ɵɵ instead of Δ for now (#29850) 2019-04-11 16:27:56 -07:00
platform-server build: hide @angular/http for Angular v8 (#29550) 2019-04-02 10:55:31 -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
terser feat(compiler-cli): export tooling definitions (#29929) 2019-04-17 17:23:01 -07:00
typings_test_ts34 build: update to TypeScript 3.4 (#29372) 2019-04-10 12:12:16 -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 fix(ivy): support providing components and dirs in tests (#29945) 2019-04-16 19:14:17 -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.