@@ -97,8 +97,8 @@ module.exports = {
97
97
98
98
You can define your own custom queries as described in the example in the
99
99
[ Helpers API] ( dom-testing-library/api-helpers.mdx ) documentation, or via the
100
- [ ` buildQueries ` ] ( dom-testing-library/api-helpers.mdx#buildqueries ) helper.
101
- Then you can use them in any render call using the ` queries ` option. To make the
100
+ [ ` buildQueries ` ] ( dom-testing-library/api-helpers.mdx#buildqueries ) helper. Then
101
+ you can use them in any render call using the ` queries ` option. To make the
102
102
custom queries available globally, you can add them to your custom render method
103
103
as shown below.
104
104
@@ -281,16 +281,12 @@ With mocha, the test command would look something like this:
281
281
mocha --require jsdom-global/register
282
282
```
283
283
284
- Note, depending on the version of Node you're running, you may also need to
285
- install @babel/polyfill (if you're using babel 7) or babel-polyfill (for babel
286
- 6).
287
-
288
284
### Skipping Auto Cleanup
289
285
290
- [ ` Cleanup ` ] ( api.mdx#cleanup ) is called after each test automatically by default if
291
- the testing framework you're using supports the ` afterEach ` global (like mocha,
292
- Jest, and Jasmine). However, you may choose to skip the auto cleanup by setting
293
- the ` RTL_SKIP_AUTO_CLEANUP ` env variable to 'true'. You can do this with
286
+ [ ` Cleanup ` ] ( api.mdx#cleanup ) is called after each test automatically by default
287
+ if the testing framework you're using supports the ` afterEach ` global (like
288
+ mocha, Jest, and Jasmine). However, you may choose to skip the auto cleanup by
289
+ setting the ` RTL_SKIP_AUTO_CLEANUP ` env variable to 'true'. You can do this with
294
290
[ ` cross-env ` ] ( https://github.com/kentcdodds/cross-env ) like so:
295
291
296
292
```
0 commit comments