honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: update links to Testing Component Scenarios page (#42385) 

PR Close #42385
This commit is contained in:
Sam Severance 2021-05-27 08:32:55 -04:00 committed by Andrew Kushnir
parent e87dbafba1
commit 17d0dd3593
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
aio/content/guide/testing-utility-apis.md
View File

@ -25,7 +25,7 @@ Here's a summary of the stand-alone functions, in order of likely utility:
<td> <td>
Runs the body of a test (`it`) or setup (`beforeEach`) function within a special _async test zone_. Runs the body of a test (`it`) or setup (`beforeEach`) function within a special _async test zone_.
See [discussion above](guide/testing-components-scenarios#waitForAsync). See [waitForAsync](guide/testing-components-scenarios#waitForAsync).
</td> </td>
</tr> </tr>
@ -38,7 +38,7 @@ Here's a summary of the stand-alone functions, in order of likely utility:
<td> <td>
Runs the body of a test (`it`) within a special _fakeAsync test zone_, enabling Runs the body of a test (`it`) within a special _fakeAsync test zone_, enabling
a linear control flow coding style. See [discussion above](guide/testing-components-scenarios#fake-async). a linear control flow coding style. See [fakeAsync](guide/testing-components-scenarios#fake-async).
</td> </td>
</tr> </tr>
@ -63,7 +63,7 @@ Here's a summary of the stand-alone functions, in order of likely utility:
Accepts an optional argument that moves the virtual clock forward Accepts an optional argument that moves the virtual clock forward
by the specified number of milliseconds, by the specified number of milliseconds,
clearing asynchronous activities scheduled within that timeframe. clearing asynchronous activities scheduled within that timeframe.
See [discussion above](guide/testing-components-scenarios#tick). See [tick](guide/testing-components-scenarios#tick).
</td> </td>
</tr> </tr>
@ -227,7 +227,7 @@ Here are the most important static methods, in order of likely utility.
Compile the testing module asynchronously after you've finished configuring it. Compile the testing module asynchronously after you've finished configuring it.
You **must** call this method if _any_ of the testing module components have a `templateUrl` You **must** call this method if _any_ of the testing module components have a `templateUrl`
or `styleUrls` because fetching component template and style files is necessarily asynchronous. or `styleUrls` because fetching component template and style files is necessarily asynchronous.
See [above](guide/testing-components-scenarios#compile-components). See [compileComponents](guide/testing-components-scenarios#compile-components).
After calling `compileComponents`, the `TestBed` configuration is frozen for the duration of the current spec. After calling `compileComponents`, the `TestBed` configuration is frozen for the duration of the current spec.
@ -540,7 +540,7 @@ Here are the most useful methods for testers.
To resume testing after completion of asynchronous activity or To resume testing after completion of asynchronous activity or
asynchronous change detection, hook that promise. asynchronous change detection, hook that promise.
See [above](guide/testing-components-scenarios#when-stable). See [whenStable](guide/testing-components-scenarios#when-stable).
</td> </td>
</tr> </tr>
@ -710,7 +710,7 @@ Here are the most useful `DebugElement` members for testers, in approximate orde
Triggers the event by its name if there is a corresponding listener Triggers the event by its name if there is a corresponding listener
in the element's `listeners` collection. in the element's `listeners` collection.
The second parameter is the _event object_ expected by the handler. The second parameter is the _event object_ expected by the handler.
See [above](guide/testing-components-scenarios#trigger-event-handler). See [triggerEventHandler](guide/testing-components-scenarios#trigger-event-handler).
If the event lacks a listener or there's some other problem, If the event lacks a listener or there's some other problem,
consider calling `nativeElement.dispatchEvent(eventObject)`. consider calling `nativeElement.dispatchEvent(eventObject)`.