Skip to content

docs: fix the harness with method's options list format in using component harnesses #20609

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 22, 2020
Merged

docs: fix the harness with method's options list format in using component harnesses #20609

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions guides/using-component-harnesses.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ provided constraints. The particular constraint options vary depending on the ha
harnesses support at least:

- `selector` - CSS selector that the component must match (in addition to its host selector, such
as `[mat-button]`)
as `[mat-button]`)
- `ancestor` - CSS selector for a some ancestor element above the component in the DOM

In addition to these standard options, `MatButtonHarness` also supports
Expand Down Expand Up @@ -156,7 +156,7 @@ it('should mark confirmed when ok button clicked', async () => {
});
```

Note that the code above has does not call `fixture.detectChanges()`, something you commonly see in
Note that the code above does not call `fixture.detectChanges()`, something you commonly see in
unit tests. The CDK's component harnesses automatically invoke change detection after performing
actions and before reading state. The harness also automatically waits for the fixture to be stable,
which will cause the test to wait for `setTimeout`, `Promise`, etc.
Expand Down