62f4140634
Initially the blocklist has been removed because there were no remaining disabled tests that failed. Also the blocklist logic didn't work anymore because the `material-unit-tests` CI job now runs against `angular/components#master` with Bazel. 388578fec946237e24521509bd887efc243a86d9 tried to revert the removal of the blocklist in favor of a new upcoming breaking change with HammerJS, but the revert doesn't help since the blocklist still doesn't work with Bazel. In order to make the blocklist work with the unit tests running with Bazel, a PR has been submitted on the components repository. See: https://github.com/angular/components/pull/16833. This commit updates the blocklist logic on the framework side to work with the new logic on the components repo side. PR Close #32239
1.2 KiB
Unit tests for Angular CDK/Material
Currently, all changes to Ivy are validated against the test suite of the
angular/components repository. Known failing tests are skipped based on
the blocklist in tools/material-ci/test-blocklist.ts.
Whenever the root cause of a known failure is identified, the notes field
for the corresponding tests should be updated. Whenever a failure is resolved,
the corresponding tests should be removed from the blocklist.
Debugging
Information on debugging can be found here.
Excluding new tests
In case there are any tests in the components test suite that fail due to
recent changes in the framework and you want to exclude the tests temporarily,
a new entry can be added to the test-blocklist.ts file.
Each property in the blocklist object corresponds to a test in the components repository. The name of the property must match the exact test name. Additionally it's recommended that every entry has a field with a note on why the test is disabled.
export const testBlocklist: any = {
'MatSlider should be able to drag thumb': {
error: 'Cannot register event "dragstart".',
notes: 'Breaking change where HammerJS module needs to be imported.'
}
}