angular-cn/integration
Alex Eagle 102ed3b03c test: move platform-server integration test (#22810)
Now it lives in our standard location for tests against npm packages

PR Close #22810
2018-04-13 16:30:50 -07:00
..
bazel test: integration tests now against bazel built packages (#22810) 2018-04-13 16:30:50 -07:00
cli-hello-world test: upgrade cli-hello-world to cli 6.0.0-rc.0 (#23149) 2018-04-04 17:47:47 -07:00
dynamic-compiler feat(core): upgrade rxjs to 6.0.0-alpha.4 (#22573) 2018-03-19 21:51:51 -07:00
hello_world__closure test: update hello_world__closure to google-closure-compiler@20180319.0.0 (#23149) 2018-04-04 17:47:47 -07:00
hello_world__systemjs_umd feat(core): upgrade rxjs to 6.0.0-alpha.4 (#22573) 2018-03-19 21:51:51 -07:00
i18n feat(core): upgrade rxjs to 6.0.0-alpha.4 (#22573) 2018-03-19 21:51:51 -07: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 style: typos fixed - https://github.com/vlajos/misspell-fixer (#22975) 2018-03-27 14:51:53 -04:00
ng_update test: add missing lockfile for integration/ng_update test (#23084) 2018-03-30 13:07:03 -07:00
platform-server test: move platform-server integration test (#22810) 2018-04-13 16:30:50 -07:00
typings_test_ts27 test: add typings test for typescript 2.7 (#23084) 2018-03-30 13:07:03 -07:00
.gitignore ci: Add back the CLI integration test with pinning (#21555) 2018-01-25 22:18:55 -08:00
README.md test: integration tests now against bazel built packages (#22810) 2018-04-13 16:30:50 -07:00
_payload-limits.json build: update zone.js to 0.8.26 to fix some regression bugs (#23227) 2018-04-09 15:16:40 -07:00
run_tests.sh test: integration tests now against bazel built packages (#22810) 2018-04-13 16:30:50 -07: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 generate integration tests such as cli-hello-world. This was generated with a current version of the CLI, and the only modification was replacement of @angular/* packages with their counterparts coming from file:../../dist/packages-dist/*. When a significant change is released in the CLI, the application should be re-generated from scratch:

$ cd integration
$ rm -rf cli-hello-world
$ ng new cli-hello-world
# Edit cli-hello-world/package.json to point the @angular packages to dist/packages-dist, and preserve local mods to
# ng build
# ng 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.

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.