angular-cn/integration
Filipe Silva df3cea41de build: add cli-hello-world-ivy-minimal test with renderComponent (#28372)
PR Close #28372
2019-02-07 12:36:51 -08:00
..
bazel build: update lock files (#28532) 2019-02-05 16:55:43 -05:00
bazel-schematics build: update lock files (#28532) 2019-02-05 16:55:43 -05:00
cli-hello-world build: update version of Angular CLI and Build Optimizer used for tests (#28372) 2019-02-07 12:36:51 -08:00
cli-hello-world-ivy-compat build: rename cli-hello-world-ivy test to cli-hello-world-ivy-compat (#28372) 2019-02-07 12:36:51 -08:00
cli-hello-world-ivy-minimal build: add cli-hello-world-ivy-minimal test with renderComponent (#28372) 2019-02-07 12:36:51 -08:00
dynamic-compiler ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494) 2019-02-01 20:22:03 -05: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 feat(core): upgrade rxjs to 6.0.0-alpha.4 (#22573) 2018-03-19 21:51:51 -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 test: add missing lockfile for integration/ng_update test (#23084) 2018-03-30 13:07:03 -07:00
ngcc fix(ivy): ngcc - identify all ESM5 decorated classes (#27848) 2019-01-11 11:14:01 -08:00
platform-server ci: pin ChromeDriver to a version compatible with docker image's Chrome (#28494) 2019-02-01 20:22:03 -05:00
typings_test_ts31 feat: add support for typescript 3.2 (#27536) 2018-12-18 13:20:01 -08:00
typings_test_ts32 test: fix outDir in TS 3.2 integration test (#27774) 2019-01-08 16:00:26 -08:00
.gitignore ci: Add back the CLI integration test with pinning (#21555) 2018-01-25 22:18:55 -08:00
README.md build: add cli-hello-world-ivy-minimal test with renderComponent (#28372) 2019-02-07 12:36:51 -08:00
_payload-limits.json build: add cli-hello-world-ivy-minimal test with renderComponent (#28372) 2019-02-07 12:36:51 -08:00
get-sharded-tests.js build: shard integration tests on circleci (#27937) 2019-01-07 15:35:09 -08:00
run_tests.sh build: add cli-hello-world-ivy-minimal test with renderComponent (#28372) 2019-02-07 12:36:51 -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 hello_world_cli contains a test for render3 used with the angular cli.

If the Angular CLI is modified to generate a render3 application this should be replaced with that project.

If the render3 is updated to support the Angular 5 bootstrap a version of this project should be created that uses the Angular 5 bootstrap.

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.