Skip to content

docs(cdk/testing): fix broken harness predicate links #19366

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

Closed
wants to merge 1 commit into from
Closed

docs(cdk/testing): fix broken harness predicate links #19366

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 src/cdk/testing/test-harnesses.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ are used to create `ComponentHarness` instances for elements under this root ele
Calls to `getHarness` and `getAllHarnesses` can either take `ComponentHarness` subclass or a
`HarnessPredicate`. `HarnessPredicate` applies additional restrictions to the search (e.g. searching
for a button that has some particular text, etc). The
[details of `HarnessPredicate`](#filtering-harness-instances-with-harnesspredicate) are discussed in
[details of `HarnessPredicate`](#filtering-harness-instances-with-code-harnesspredicate-code-) are discussed in
the [API for component harness authors](#api-for-component-harness-authors); harness authors should
provide convenience methods on their `ComponentHarness` subclass to facilitate the creation of
`HarnessPredicate` instances. However, if the harness author's API is not sufficient, they can be
Expand Down Expand Up @@ -216,7 +216,7 @@ class MyPopupHarness extends ComponentHarness {

While `ComponentHarness` subclasses require only the `hostSelector` property, most harnesses should
also implement a static `with` method to generate `HarnessPredicate` instances. The
[`HarnessPredicate`](#filtering-harness-instances-with-harnesspredicate) section below covers this
[`HarnessPredicate`](#filtering-harness-instances-with-code-harnesspredicate-code-) section below covers this
in more detail.

#### Finding elements in the component's DOM
Expand Down