Skip to content

Commit 02f206b

Browse files
authored
Merge pull request #2918 from Madobyte/update-part10d
Update part10d.md
2 parents 03a5360 + 34eb835 commit 02f206b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/content/10/en/part10d.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ src/
106106
...
107107
```
108108

109-
In this example, the component's code is in the <i>index.jsx</i> file and the test in the <i>AppBar.test.jsx</i> file. Note that in order to Jest finding your test files you either have to put them into a <i>\_\_tests\_\_</i> directory, use the <i>.test</i> or <i>.spec</i> suffix, or [manually configure](https://jestjs.io/docs/en/configuration#testmatch-arraystring) the global patterns.
109+
In this example, the component's code is in the <i>index.jsx</i> file and the test in the <i>AppBar.test.jsx</i> file. Note that in order for Jest to find your test files you either have to put them into a <i>\_\_tests\_\_</i> directory, use the <i>.test</i> or <i>.spec</i> suffix, or [manually configure](https://jestjs.io/docs/en/configuration#testmatch-arraystring) the global patterns.
110110

111111
### Testing components
112112

@@ -178,7 +178,7 @@ We acquire the <em>Text</em> node containing certain text by using the <em>getBy
178178

179179
React Native Testing Library's documentation has some good hints on [how to query different kinds of elements](https://callstack.github.io/react-native-testing-library/docs/how-should-i-query). Another guide worth reading is Kent C. Dodds article [Making your UI tests resilient to change](https://kentcdodds.com/blog/making-your-ui-tests-resilient-to-change).
180180

181-
The object [screen](https://callstack.github.io/react-native-testing-library/docs/api#screen) has also a helper method [debug](https://callstack.github.io/react-native-testing-library/docs/api#debug) that prints the rendered React tree in a user-friendly format. Use it if you are unsure what the React tree rendered by the <em>render</em> function looks like.
181+
The object [screen](https://callstack.github.io/react-native-testing-library/docs/api#screen) also has a helper method [debug](https://callstack.github.io/react-native-testing-library/docs/api#debug) that prints the rendered React tree in a user-friendly format. Use it if you are unsure what the React tree rendered by the <em>render</em> function looks like.
182182

183183
For all available queries, check the React Native Testing Library's [documentation](https://callstack.github.io/react-native-testing-library/docs/api-queries). The full list of available React Native specific matchers can be found in the [documentation](https://github.com/testing-library/jest-native#matchers) of the jest-native library. Jest's [documentation](https://jestjs.io/docs/en/expect) contains every universal Jest matcher.
184184

@@ -562,7 +562,7 @@ This screenshot has been taken after invalid form submission to present what the
562562

563563
Implement a sign up form for registering a user using Formik. The form should have three fields: username, password, and password confirmation. Validate the form using Yup schema so that it contains the following validations:
564564

565-
- Username is a required string with a length between 1 and 30
565+
- Username is a required string with a length between 5 and 30
566566
- Password is a required string with a length between 5 and 50
567567
- Password confirmation matches the password
568568

0 commit comments

Comments
 (0)