@@ -48,8 +48,8 @@ learn how to use a specific harness.
4848
4949These classes correspond to different implementations of the component harness system with bindings
5050for specific test environments. Any given test must only import _ one_ of these classes. Karma-based
51- unit tests should use the ` TestbedHarnessEnvironment ` , while Selenium Webdriver -based end-to-end tests
52- should use the ` SeleniumWebdriverHarnessEnvironment ` . Additional environments require custom bindings; see
51+ unit tests should use the ` TestbedHarnessEnvironment ` , while Selenium WebDriver -based end-to-end tests
52+ should use the ` SeleniumWebDriverHarnessEnvironment ` . Additional environments require custom bindings; see
5353[ API for harness environment authors] ( #api-for-harness-environment-authors ) for more information on
5454alternate test environments.
5555
@@ -113,7 +113,7 @@ it('loads harnesses', async () => {
113113| ------ | ----------- |
114114| ` loader(): HarnessLoader ` | Gets a ` HarnessLoader ` instance for the current HTML document, rooted at the document's root element. |
115115
116- Since Selenium Webdriver does not deal with fixtures, the API in this environment is simpler. The
116+ Since Selenium WebDriver does not deal with fixtures, the API in this environment is simpler. The
117117` HarnessLoader ` returned by the ` loader() ` method should be sufficient for loading all necessary
118118` ComponentHarness ` instances.
119119
@@ -304,7 +304,7 @@ The functions created with the locator methods described above all return `TestE
304304| ` dispatchEvent(name: string, data?: Record<string, EventData>): Promise<void>; ` | Dispatches an event with a particular name. |
305305
306306` TestElement ` is an abstraction designed to work across different test environments (Karma,
307- Selenium Webdriver , etc). When using harnesses, you should perform all DOM interaction via this interface.
307+ Selenium WebDriver , etc). When using harnesses, you should perform all DOM interaction via this interface.
308308Other means of accessing DOM elements (e.g. ` document.querySelector ` ) will not work in all test
309309environments.
310310
@@ -574,7 +574,7 @@ may need to explicitly wait for tasks outside `NgZone`, as this does not happen
574574
575575Harness environment authors are developers who want to add support for using component harnesses in
576576additional testing environments. Out-of-the-box, Angular CDK's component harnesses can be used in
577- Selenium Webdriver E2E tests and Karma unit tests. Developers can support additional environments by
577+ Selenium WebDriver E2E tests and Karma unit tests. Developers can support additional environments by
578578creating custom implementations of ` TestElement ` and ` HarnessEnvironment ` .
579579
580580#### Creating a ` TestElement ` implementation for the environment
@@ -583,7 +583,7 @@ The first step in adding support for a new testing environment is to create a `T
583583implementation. The ` TestElement ` interface serves as an environment-agnostic representation of a
584584DOM element; it lets harnesses interact with DOM elements regardless of the underlying environment.
585585Because some environments don't support interacting with DOM elements synchronously
586- (e.g. webdriver ), all of the ` TestElement ` methods are asynchronous, returning a ` Promise ` with the
586+ (e.g. WebDriver ), all of the ` TestElement ` methods are asynchronous, returning a ` Promise ` with the
587587result of the operation.
588588
589589| Method | Description |
0 commit comments