✅ Deploy Preview for testing-library ready!

Name	Link
🔨 Latest commit	32aa938
🔍 Latest deploy log	https://app.netlify.com/sites/testing-library/deploys/653febfcdc6d560008cf1927
😎 Deploy Preview	https://deploy-preview-1330--testing-library.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Hi @kyle-n!
Thanks for taking the time to write this.
Any chance to align this explanation with what we have in testing-libarry/react?
You can see it here.
It also feels like a rephrasing there can help to state that globals: true is needed if you want to take it :)

@MatanBobi Thanks for the feedback!

I rephrased the message under cleanup() to match the React documentation. I also shortened the message, which hopefully makes it easier to read, and copied it to the other frameworks that use cleanup and only run it with a global afterEach.

Does this phrasing work for cleanup?

This is called automatically if your testing framework (such as mocha, Jest or Jasmine) injects a global afterEach() function into the testing environment.

That's cool but I'm still missing the "If not, you will need to do manual cleanups after each test" because it's important information IMO. Wdyt?

I thought that sentence was redundant, since the previous sentence implies if cleanup() is only run automatically with a global afterEach(), it is not run without one. However, on second thought, it is better to be explicit and clear. Updated.

@all-contributors please add @kyle-n for docs :)

@MatanBobi

I've put up a pull request to add @kyle-n! 🎉