honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: add Ivy and View Engine test scripts (#38149) 

Developer docs previously stated to use `yarn bazel test //packages/...` which attempts to test all packages with View
Engine (the default), even though not all support View Engine. This updates the doc to use `yarn test-ivy-aot` and
`yarn test-non-ivy` which tests both Ivy and View Engine while filtering out tests which are not compatible with each
renderer.

PR Close #38149
This commit is contained in:
Doug Parker 2020-07-20 16:05:04 -07:00 committed by Andrew Kushnir
parent 5e742d29d0
commit d88711c2fc
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/DEVELOPER.md
View File

@ -80,8 +80,10 @@ Bazel is used as the primary tool for building and testing Angular. Building and
incremental with Bazel, and it's possible to only run tests for an individual package instead incremental with Bazel, and it's possible to only run tests for an individual package instead
of for all packages. Read more about this in the [BAZEL.md](./BAZEL.md) document. of for all packages. Read more about this in the [BAZEL.md](./BAZEL.md) document.
You should execute all test suites before submitting a PR to GitHub: You should execute all test suites before submitting a PR to GitHub. Note that not all tests
- `yarn bazel test packages/...` support both Ivy and View Engine, so they need to be run separately:
- `yarn test-ivy-aot //packages/...`
- `yarn test-non-ivy //packages/...`
**Note**: The first test run will be much slower than future runs. This is because future runs will **Note**: The first test run will be much slower than future runs. This is because future runs will
benefit from Bazel's capability to do incremental builds. benefit from Bazel's capability to do incremental builds.