DEVELOPER.md (angular-13.3.9) | : | DEVELOPER.md (angular-13.3.10) | ||
---|---|---|---|---|
skipping to change at line 77 | skipping to change at line 77 | |||
To build Angular run: | To build Angular run: | |||
```shell | ```shell | |||
node ./scripts/build/build-packages-dist.js | node ./scripts/build/build-packages-dist.js | |||
``` | ``` | |||
* Results are put in the `dist/packages-dist` folder. | * Results are put in the `dist/packages-dist` folder. | |||
## Running Tests Locally | ## Running Tests Locally | |||
Bazel is used as the primary tool for building and testing Angular. Building and | Bazel is used as the primary tool for building and testing Angular. | |||
testing are | ||||
incremental with Bazel, and it's possible to only run tests for an individual pa | ||||
ckage 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 test //packages/...` | ||||
**Note**: The ellipsis in the commands above is not meant to be substituted by a | ||||
package name, but | ||||
is used by Bazel as a wildcard to execute all tests in the specified path. To ex | ||||
ecute tests for a | ||||
single package, the commands are (exemplary): | ||||
- `yarn test //packages/core/...` for all tests, or | ||||
- `yarn test //packages/core/test:test_web_firefox` for a particular test suite. | ||||
**Note**: The first test run will be much slower than future runs. This is becau | To see how to run and debug Angular tests locally please refer to the Bazel [Tes | |||
se future runs will | ting Angular](./BAZEL.md#testing-angular) section. | |||
benefit from Bazel's capability to do incremental builds. | ||||
All the tests are executed on our Continuous Integration infrastructure. PRs can | Note that you should execute all test suites before submitting a PR to GitHub (` | |||
only be | yarn test //packages/...`). | |||
merged if the code is formatted properly and all tests are passing. | ||||
However, affected tests will be executed on our CI infrastructure. So if you for | ||||
got to run some affected tests which would fail, GitHub will indicate the error | ||||
state and present you the failures. | ||||
PRs can only be merged if the code is formatted properly and all tests are passi | ||||
ng. | ||||
<a name="formatting-your-source-code"> | <a name="formatting-your-source-code"> | |||
<a name="clang-format"></a> | <a name="clang-format"></a> | |||
### Testing changes against a local library/project | ### Testing changes against a local library/project | |||
Often for developers the best way to ensure the changes they have made work as e xpected is to run | Often for developers the best way to ensure the changes they have made work as e xpected is to run | |||
use changes in another library or project. To do this developers can build Angul ar locally, and | use changes in another library or project. To do this developers can build Angul ar locally, and | |||
using `yarn link` build a local project with the created artifacts. | using `yarn link` build a local project with the created artifacts. | |||
End of changes. 3 change blocks. | ||||
23 lines changed or deleted | 12 lines changed or added |