From 861d94baebdc4039938de6478f68046d27729aad Mon Sep 17 00:00:00 2001 From: Maxime Veber Date: Tue, 2 Aug 2022 17:05:59 +0200 Subject: [PATCH] fix: formatting of mocking module paragraph --- 7-testing/7.4-mocking-rn-modules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/7-testing/7.4-mocking-rn-modules.md b/7-testing/7.4-mocking-rn-modules.md index b37220d..6156e98 100644 --- a/7-testing/7.4-mocking-rn-modules.md +++ b/7-testing/7.4-mocking-rn-modules.md @@ -18,7 +18,7 @@ While Jest supports a bunch of methods for mocking utilities, we suggest doing m └── node_modules ``` -As you can see above, you can mock both node_modules and your custom defined JS files. +As you can see above, you can mock both node\_modules and your custom defined JS files. Whenever you import `utils/language.util` file, Jest will automatically read it from `__mocks__/language.util.js`. If you would like to un-mock a file and read the real source code instead of mocking it, you could do that using `jest.unmock('module_path')` function in the test case.