angular-cn/integration/cli-hello-world-ivy-compat
Greg Magolan dde68ff954 build: add npm_integration_test && angular_integration_test (#33927)
* it's tricky to get out of the runfiles tree with `bazel test` as `BUILD_WORKSPACE_DIRECTORY` is not set but I employed a trick to read the `DO_NOT_BUILD_HERE` file that is one level up from `execroot` and that contains the workspace directory. This is experimental and if `bazel test //:test.debug` fails than `bazel run` is still guaranteed to work as  `BUILD_WORKSPACE_DIRECTORY` will be set in that context

* test //integration:bazel_test and //integration:bazel-schematics_test exclusively

* run "exclusive" and "manual" bazel-in-bazel integration tests in their own CI job as they take 8m+ to execute

```
//integration:bazel-schematics_test                                      PASSED in 317.2s
//integration:bazel_test                                                 PASSED in 167.8s
```

* Skip all integration tests that are now handled by angular_integration_test except the tests that are tracked for payload size; these are:
- cli-hello-world*
- hello_world__closure

* add & pin @babel deps as newer versions of babel break //packages/localize/src/tools/test:test

@babel/core dep had to be pinned to 7.6.4 or else //packages/localize/src/tools/test:test failed. Also //packages/localize uses @babel/generator, @babel/template, @babel/traverse & @babel/types so these deps were added to package.json as they were not being hoisted anymore from @babel/core transitive.

NB: integration/hello_world__systemjs_umd test must run with systemjs 0.20.0
NB: systemjs must be at 0.18.10 for legacy saucelabs job to pass
NB: With Bazel 2.0, the glob for the files to test `"integration/bazel/**"` is empty if integation/bazel is in .bazelignore. This glob worked under these conditions with 1.1.0. I did not bother testing with 1.2.x as not having integration/bazel in .bazelignore is correct.

PR Close #33927
2020-02-24 08:59:18 -08:00
..
e2e test: use puppeteer in integration tests and to download correct chromedriver (#35049) 2020-02-11 13:16:52 -08:00
src test: update integration/cli-hello-world-ivy-compat project structure (#33175) 2019-10-21 15:54:06 -04:00
.editorconfig build: rename cli-hello-world-ivy test to cli-hello-world-ivy-compat (#28372) 2019-02-07 12:36:51 -08:00
.gitignore test: update integration/cli-hello-world-ivy-compat project structure (#33175) 2019-10-21 15:54:06 -04:00
README.md test: update integration/cli-hello-world-ivy-compat project structure (#33175) 2019-10-21 15:54:06 -04:00
angular.json test: update integration/cli-hello-world-ivy-compat project structure (#33175) 2019-10-21 15:54:06 -04:00
browserslist test: update integration/cli-hello-world-ivy-compat project structure (#33175) 2019-10-21 15:54:06 -04:00
debug-test.sh build: fix build scripts on macOS (#33854) 2019-11-15 16:05:00 -08:00
karma.conf.js test: use puppeteer in integration tests and to download correct chromedriver (#35049) 2020-02-11 13:16:52 -08:00
package.json build: add npm_integration_test && angular_integration_test (#33927) 2020-02-24 08:59:18 -08:00
tsconfig.app.json test: update integration/cli-hello-world-ivy-compat project structure (#33175) 2019-10-21 15:54:06 -04:00
tsconfig.json test: update integration/cli-hello-world-ivy-compat project structure (#33175) 2019-10-21 15:54:06 -04:00
tsconfig.spec.json test: update integration/cli-hello-world-ivy-compat project structure (#33175) 2019-10-21 15:54:06 -04:00
tslint.json test: update integration/cli-hello-world-ivy-compat project structure (#33175) 2019-10-21 15:54:06 -04:00
yarn.lock test: use puppeteer in integration tests and to download correct chromedriver (#35049) 2020-02-11 13:16:52 -08:00

README.md

CliHelloWorldIvy

This project was generated with Angular CLI version 9.0.0-next.9.

Development server

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Running unit tests

Run ng test to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e to execute the end-to-end tests via Protractor.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.