Skip to content

Commit 2119abf

Browse files
dgp1130Splaktar
authored andcommitted
docs: add Ivy and View Engine test scripts (angular#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 angular#38149
1 parent fc728d0 commit 2119abf

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/DEVELOPER.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -80,8 +80,10 @@ Bazel is used as the primary tool for building and testing Angular. Building and
8080
incremental with Bazel, and it's possible to only run tests for an individual package instead
8181
of for all packages. Read more about this in the [BAZEL.md](./BAZEL.md) document.
8282

83-
You should execute all test suites before submitting a PR to GitHub:
84-
- `yarn bazel test packages/...`
83+
You should execute all test suites before submitting a PR to GitHub. Note that not all tests
84+
support both Ivy and View Engine, so they need to be run separately:
85+
- `yarn test-ivy-aot //packages/...`
86+
- `yarn test-non-ivy //packages/...`
8587

8688
**Note**: The first test run will be much slower than future runs. This is because future runs will
8789
benefit from Bazel's capability to do incremental builds.

0 commit comments

Comments
 (0)