bug(MatCheckboxHarness): isChecked() returns false right after check()

Reproduction

MatCheckboxHarness.isChecked() does not return true right after check() has been called on the harness:

const checkbox = await loader.getHarness(MatCheckboxHarness.with({selector: [formControlName="myFormControl"]})); 
await checkbox.check();
expect(await checkbox.isChecked()).toBeTruthy();

If the checkbox gets checked some other controls will be displayed. There is another test testing successfully for these controls after the call to MatCheckboxHarness.check(). Therefore I’m sure that check() is working okay but isChecked() does not worked as intended.

Expected Behavior

MatCheckboxHarness.isChecked() returns true right after check() has been called

Actual Behavior

MatCheckboxHarness.isChecked() returns false right after check() has been called

Environment

• Angular/CDK/Material: $ npm list --depth 0 smartapplianceenabler@0.0.0 /data/IdeaProjects/SmartApplianceEnabler/src/main/angular ├── @angular-devkit/build-angular@0.901.1 ├── @angular/animations@9.1.1 ├── @angular/cdk@9.2.0 ├── @angular/cli@9.1.1 ├── @angular/common@9.1.1 ├── @angular/compiler@9.1.1 ├── @angular/compiler-cli@9.1.1 ├── @angular/core@9.1.1 ├── @angular/flex-layout@9.0.0-beta.29 ├── @angular/forms@9.1.1 ├── @angular/language-service@9.1.1 ├── @angular/material@9.2.0 ├── @angular/platform-browser@9.1.1 ├── @angular/platform-browser-dynamic@9.1.1 ├── @angular/router@9.1.1 ├── @ngx-translate/core@10.0.2 ├── @ngx-translate/http-loader@3.0.1 ├── @types/jest@24.9.1 ├── @types/node@12.12.35 ├── clockpicker@0.0.7 ├── include-media@1.4.9 ├── UNMET PEER DEPENDENCY jest@24.9.0 ├── jest-preset-angular@8.1.3 ├── jquery@3.5.0 ├── moment@2.24.0 ├── rxjs@6.5.5 ├── ts-node@7.0.1 ├── tslib@1.11.1 ├── tslint@5.11.0 ├── typescript@3.8.3 └── zone.js@0.10.3

• Operating System (e.g. Windows, macOS, Ubuntu): Ubuntu 18.04

[camueller]

Great - looks like you found the source of the problem 😃

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}