From 8461259334bd0d73a817370b07a2e6cf5e99f9cd Mon Sep 17 00:00:00 2001 From: Nathan Nontell Date: Fri, 20 May 2022 13:39:44 -0400 Subject: [PATCH] docs(docs-infra): update createComponent description to fix incorrect method name and invalid use of html escaping (#46074) PR Close #46074 --- aio/content/guide/testing-utility-apis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/testing-utility-apis.md b/aio/content/guide/testing-utility-apis.md index 31bd117f915..dd109e3f2f2 100644 --- a/aio/content/guide/testing-utility-apis.md +++ b/aio/content/guide/testing-utility-apis.md @@ -68,7 +68,7 @@ Here are the most important static methods, in order of likely utility. |:--- |:--- | | `configureTestingModule` | The testing shims \(`karma-test-shim`, `browser-test-shim`\) establish the [initial test environment](guide/testing) and a default testing module. The default testing module is configured with basic declaratives and some Angular service substitutes that every tester needs.
Call `configureTestingModule` to refine the testing module configuration for a particular set of tests by adding and removing imports, declarations \(of components, directives, and pipes\), and providers. | | `compileComponents` | 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` or `styleUrls` because fetching component template and style files is necessarily asynchronous. See [compileComponents](guide/testing-components-scenarios#compile-components).
After calling `compileComponents`, the `TestBed` configuration is frozen for the duration of the current spec. | -| `createComponent<T>` | Create an instance of a component of type `T` based on the current `TestBed` configuration. After calling `compileComponent`, the `TestBed` configuration is frozen for the duration of the current spec. | +| `createComponent` | Create an instance of a component of type `T` based on the current `TestBed` configuration. After calling `createComponent`, the `TestBed` configuration is frozen for the duration of the current spec. | | `overrideModule` | Replace metadata for the given `NgModule`. Recall that modules can import other modules. The `overrideModule` method can reach deeply into the current testing module to modify one of these inner modules. | | `overrideComponent` | Replace metadata for the given component class, which could be nested deeply within an inner module. | | `overrideDirective` | Replace metadata for the given directive class, which could be nested deeply within an inner module. |