edd5f5a333
We now create 2 programs with exactly the same fileNames and
exactly the same `import` / `export` declarations,
allowing TS to reuse the structure of first program
completely. When passing in an oldProgram and the files didn’t change,
TS can also reuse the old program completely.
This is possible buy adding generated files to TS
in `host.geSourceFile` via `ts.SourceFile.referencedFiles`.
This commit also:
- has a minor side effect on how we generate shared stylesheets:
- previously every import in a stylesheet would generate a new
`.ngstyles.ts` file.
- now, we only generate 1 `.ngstyles.ts` file per entry in `@Component.styleUrls`.
This was required as we need to be able to determine the program files
without loading the resources (which can be async).
- makes all angular related methods in `CompilerHost`
optional, allowing to just use a regular `ts.CompilerHost` as `CompilerHost`.
- simplifies the logic around `Compiler.analyzeNgModules` by introducing `NgAnalyzedFile`.
Perf impact: 1.5s improvement in compiling angular io
PR Close #19275
|
||
|---|---|---|
| .. | ||
| bazel | ||
| hello_world__closure | ||
| hello_world__systemjs_umd | ||
| i18n | ||
| language_service_plugin | ||
| typings_test_ts24 | ||
| .gitignore | ||
| README.md | ||
| _payload-limits.sh | ||
| ng-cli-create.sh | ||
| run_tests.sh | ||
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.jsonfile - The test runner will run
yarnandyarn teston 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