angular-cn/integration
Keen Yee Liau b1e099b657 fix(bazel): fix integration test for bazel-schematics (#28460)
With the release of @angular/bazel v7.2.3, the npm install step right
after `ng new` installs this version. However there is a bug in the
builder which results in bazel executable not found.

This bug was not discovered before because the dependencies of the
project created by `ng new` are not pinned.

The fix is to pin the version of @angular/bazel to 7.2.2 which relies on
global installation of bazel.

PR Close #28460
2019-01-30 19:05:11 -05:00
..
bazel build: create dist/bin symlink with Bazel outputs (#27781) 2019-01-22 09:52:46 -08:00
bazel-schematics fix(bazel): fix integration test for bazel-schematics (#28460) 2019-01-30 19:05:11 -05:00
cli-hello-world test: log cli version in `cli-hello-world[-ivy]` integration projects (#26947) 2019-01-28 14:01:13 -08:00
cli-hello-world-ivy test: log cli version in `cli-hello-world[-ivy]` integration projects (#26947) 2019-01-28 14:01:13 -08:00
dynamic-compiler build(bazel): Use local rollup & build-optimizer for ng_rollup_bundle (#28215) 2019-01-18 09:07:52 -08:00
hello_world__closure feat(ivy): implement TestBed (#25369) 2018-08-14 11:58: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(ivy): implement TestBed (#25369) 2018-08-14 11:58:47 -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 test(language-service): Improve integration test (#28168) 2019-01-17 14:11:28 -08:00
ng_elements test: make `elements` integration tests less flaky (#26869) 2018-11-02 10:37:34 -07: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 test: fix integration/platform-server test which had missing @types/node devDep (#27937) 2019-01-07 15:35:09 -08: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: upgrade `@angular/cli` in `cli-hello-world` integration test (#26869) 2018-11-02 10:37:35 -07:00
_payload-limits.json build: upgrade `cli-hello-world[-ivy]` integration projects to @angular/cli@7.2.1 (#27697) 2019-01-22 12:02:10 -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: shard integration tests on circleci (#27937) 2019-01-07 15:35:09 -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.

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.