Goals and usage of test-utils are unclear in docs

• I have searched the issues of this repository and believe that this is not a duplicate.

I’m trying to use material-ui@next with react-testing-library, which does not use Enzyme, and I find the purpose and use cases of test-utils unclear in the userspace docs. I have used Enzyme previously so I understand the difference between mount/shallow/render, but not how they differ from Enzyme, as I can successfully unit test components with Enzyme directly. Meanwhile, it seems like testing libraries like react-testing-library, which do not use Enzyme renderers, cannot be used with the built in test-utils. I would appreciate more information on what test-utils do differently from a practical perspective (not just adding context to components or wrapping Enzyme for installation convenience) so I can decide when I need to use them over a different testing library.

[oliviertassinari]

Most of the value of our helpers come from:

• the mount cleanUp API that cleans the DOM from anything that could have been mounted. It fixes enzyme issues like https://github.com/airbnb/enzyme/issues/935 or https://github.com/airbnb/enzyme/issues/911#issuecomment-317351800.
• untilSelector to dive into a chain of higher-order components. It fixes enzyme issues like https://github.com/airbnb/enzyme/issues/539.

[nickmccurdy]

Thanks, I was under the impression that they were somehow required or I would at least be shooting myself in the foot with incompatibility if I didn’t.