angular-cn/integration
Georgios Kalpakas 9684d78cae build: update `concurrently` to latest version
The regression in `concurrently` v3.2.0 (which made us roll back to v3.1.0
in #14378) has been fixed in v3.3.0 (see kimmobrunfeldt/concurrently#89).
2017-05-03 09:35:57 -07:00
..
hello_world__closure build: update `concurrently` to latest version 2017-05-03 09:35:57 -07:00
hello_world__systemjs_umd build: update `concurrently` to latest version 2017-05-03 09:35:57 -07:00
language_service_plugin ci(language-service): update ci tests to official 2.3 build (#16415) 2017-04-28 17:40:53 -05:00
typings_test_ts21 fix: strictNullCheck support. (#16389) (#16389) 2017-04-28 09:15:00 -05:00
typings_test_ts22 fix: strictNullCheck support. (#16389) (#16389) 2017-04-28 09:15:00 -05:00
.gitignore perf: distrubute smaller bundled code and include es2015 bundle 2017-02-21 20:48:55 -08:00
README.md refactor: update paths from modules/@angular to packages 2017-03-08 16:29:28 -08:00
build_rxjs_es6.sh test(integration): add an env for testing closure builds (#14130) 2017-01-27 09:17:50 -08:00
run_tests.sh perf: distrubute smaller bundled code and include es2015 bundle 2017-02-21 20:48:55 -08:00
rxjs.tsconfig.json fix: build and test fixes for TS 2.1 (#13294) 2017-02-08 11:32:40 -06: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

The first time you run the tests, you'll need some setup:

$ ./integration/build_rxjs_es6.sh

Now 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