angular-docs-cn/integration/cli-hello-world-lazy
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: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04:00
.editorconfig test: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04:00
.gitignore test: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04:00
README.md test: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04:00
angular.json test: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04:00
browserslist test: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04:00
check-output-for-ngdevmode.js test: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04: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: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04:00
tsconfig.json test: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04:00
tsconfig.spec.json test: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -04:00
tslint.json test: add integration test for lazy chunks and ngDevMode in cli apps (#32957) 2019-10-21 11:27:43 -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

CliHelloWorldLazy

This test checks bundle sizes when there is a lazy module. It also checks if the ngDevMode global variable and string references in packages/core/src/util/ng_dev_mode.ts are correctly removed.

This test contains a lazy route to ensure ngDevMode removal happens even across chunks, and a payload size check in ../_payload-limits.json to ensure extra code is not retained accidentally.