2019-01-14 20:47:39 -05:00
|
|
|
### Unit tests for Angular CDK/Material
|
|
|
|
|
The unit tests from angular/material2 run on CircleCI under the `material-unit-tests` job.
|
2019-02-05 13:48:18 -05:00
|
|
|
Known failing tests are skipped based on the blocklist in
|
|
|
|
|
`tools/material-ci/angular_material_test_blocklist.js`. Whenever the root cause of a known failure
|
2019-01-14 20:47:39 -05:00
|
|
|
is identified, the `notes` field for the corresponding tests should be updated. Whenever a failure
|
2019-02-05 13:48:18 -05:00
|
|
|
is resolved, the corresponding tests should be removed from the blocklist.
|
2019-01-14 20:47:39 -05:00
|
|
|
|
|
|
|
|
### Debugging
|
|
|
|
|
To debug a failure, you need to work against the angular/material2 repo:
|
|
|
|
|
1. Clone `angular/material2`
|
|
|
|
|
2. Checkout the `ivy-2019` branch
|
|
|
|
|
3. Run `yarn`
|
|
|
|
|
4. Run `scripts/ivy/install-angular.sh path/to/local/angular/repo`
|
|
|
|
|
5. Run `gulp test`
|
|
|
|
|
|
2019-02-05 13:48:18 -05:00
|
|
|
### Regenerating the blocklist
|
|
|
|
|
If a problem has been fixed, you can regenerate the blocklist by:
|
2019-01-14 20:47:39 -05:00
|
|
|
1. Clone `angular/material2`
|
|
|
|
|
2. Checkout the `ivy-2019` branch
|
|
|
|
|
3. Run `yarn`
|
|
|
|
|
4. Run `scripts/ivy/install-angular.sh path/to/local/angular/repo`
|
|
|
|
|
5. Run `gulp test`. Let it finish. It will take a few minutes.
|
2019-02-21 10:42:29 -05:00
|
|
|
6. Run `scripts/ivy/generate-blocklist.js path/to/local/angular/repo`
|
2019-02-05 13:48:18 -05:00
|
|
|
7. Copy the new blocklist from `dist/angular_material_test_blocklist.js`
|
