<!-- * Please fill out this template with all the relevant information so we can understand what's going on and fix the issue. We appreciate bugs filed and PRs submitted! * Please make sure that you are familiar with and follow the Code of Conduct for this project (found in the CODE_OF_CONDUCT.md file). We'll probably ask you to submit the fix (after giving some direction). If you've never done that before, that's great! Check this free short video tutorial to learn how: http://kcd.im/pull-request --> - `@testing-library/jest-dom` version: 5.14.1 - `node` version: v16.7.0 - `npm` (or `yarn`) version: 7.21.0 - `@testing-library/react` version: 12.0.0 ### Relevant code or config: ```js expect(document.body).toHaveClass('abc', { exact: true }); ``` ### What you did: <!-- What you were doing --> Testing an element's exact `class` ### What happened: <!-- Please provide the full error message/screenshots/anything --> When the assertion fails, the output is garbled:  ### Reproduction: <!-- If possible, please create a repository that reproduces the issue with the minimal amount of code possible. Or if you can, try to reproduce the issue in a Codesandbox. You can fork the one here: https://codesandbox.io/s/5z6x4r7n0p --> See relevant code above. ### Problem description: <!-- Please describe why the current behavior is a problem --> Well it's not the expected output that's for sure. ### Suggested solution: <!-- It's ok if you don't have a suggested solution, but it really helps if you could do a little digging to come up with some suggestion of how to improve things. --> Should work similarly to when `exact: false` is used: 