From da8ef8b0f6369e42e5865ef2c5a7dbf8b0beb34b Mon Sep 17 00:00:00 2001 From: Toru Kobayashi Date: Wed, 2 Sep 2020 16:31:52 +0900 Subject: [PATCH] Explain where act comes from (#3237) Co-authored-by: Sebastian Silbermann --- content/docs/testing-recipes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/testing-recipes.md b/content/docs/testing-recipes.md index d65f1742..298b867a 100644 --- a/content/docs/testing-recipes.md +++ b/content/docs/testing-recipes.md @@ -57,7 +57,7 @@ You may use a different pattern, but keep in mind that we want to execute the cl ### `act()` {#act} -When writing UI tests, tasks like rendering, user events, or data fetching can be considered as "units" of interaction with a user interface. React provides a helper called `act()` that makes sure all updates related to these "units" have been processed and applied to the DOM before you make any assertions: +When writing UI tests, tasks like rendering, user events, or data fetching can be considered as "units" of interaction with a user interface. `react-dom/test-utils` provides a helper called [`act()`](/docs/test-utils.html#act) that makes sure all updates related to these "units" have been processed and applied to the DOM before you make any assertions: ```js act(() => {