angular-cn/integration
Alex Eagle fef3d2ad53 build: ngc-wrapped as a bazel worker (#18960)
PR Close #18960
2017-09-01 12:23:11 -05:00
..
bazel build: ngc-wrapped as a bazel worker (#18960) 2017-09-01 12:23:11 -05:00
hello_world__closure build: publish tree of files rather than FESMs (#18541) 2017-08-31 15:34:50 -07:00
hello_world__systemjs_umd build: update `concurrently` to latest version 2017-05-03 09:35:57 -07:00
i18n build: publish tree of files rather than FESMs (#18541) 2017-08-31 15:34:50 -07:00
language_service_plugin fix(language-service): remove tsickle dependency 2017-08-16 11:33:49 -07:00
typings_test_ts22 refactor(tsc-wrapped): move tsc-wrapped to the packages directory (#18160) 2017-07-21 12:26:16 -05:00
typings_test_ts23 refactor(tsc-wrapped): move tsc-wrapped to the packages directory (#18160) 2017-07-21 12:26:16 -05:00
.gitignore test: add cli integration test (#18738) 2017-08-16 22:00:36 -05:00
README.md test: cleanup rxjs custom build 2017-05-04 15:07:27 -04:00
_payload-limits.sh build: fix size limits for CLI to make CI green (#18849) 2017-08-23 13:04:19 -07:00
ng-cli-create.sh build: fix build; missing firebase-tools 2017-08-25 08:17:13 -07:00
run_tests.sh build: fix build by pinning angular-cli to specific version (#18865) 2017-08-24 09:34:43 -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.

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-shrinkwrapped) dependencies. If in doubt you can install the package directly from file:../../node_modules. For example, this is useful for protractor, which has a slow post-install step (webdriver-manager update) that can be skipped when the package from Angular's node_modules is installed.

Running integration tests

You can iterate on the tests by keeping the dist folder up-to-date. See the package.json of the test(s) you're debugging, to see which dist/ folders they install from. Then run the right tsc --watch command to keep those dist folders up-to-date, for example:

$ ./node_modules/.bin/tsc -p packages/core/tsconfig-build.json --watch

Now you can run the integration test, it will re-install from the dist/ folder on each run.

$ ./integration/run_tests.sh