From d88711c2fcdf85dfccb142b53479a080f72b8391 Mon Sep 17 00:00:00 2001 From: Doug Parker Date: Mon, 20 Jul 2020 16:05:04 -0700 Subject: [PATCH] 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 --- docs/DEVELOPER.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/DEVELOPER.md b/docs/DEVELOPER.md index 340f3194ea..0cb401ab7a 100644 --- a/docs/DEVELOPER.md +++ b/docs/DEVELOPER.md @@ -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 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: -- `yarn bazel test packages/...` +You should execute all test suites before submitting a PR to GitHub. Note that not all tests +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 benefit from Bazel's capability to do incremental builds.