fix: Suggest using toBeEmptyDOMElement instead of toBeEmpty (#284)

* Suggest using toBeEmptyDOMElement instead of toBeEmpty
* fixed toBeEmptyDOMElement regular expression

Author: brrianalexis

src/__tests__/to-have-text-content.js

@@ -83,12 +83,12 @@ describe('.toHaveTextContent', () => {
     )
   })
 
-  test('when matching with empty string and element with content suggest using toBeEmpty instead', () => {
+  test('when matching with empty string and element with content, suggest using toBeEmptyDOMElement instead', () => {
     // https://github.com/testing-library/jest-dom/issues/104
     const {container} = render('<span>not empty</span>')
 
     expect(() =>
       expect(container.querySelector('span')).toHaveTextContent(''),
-    ).toThrowError(/toBeEmpty()/)
+    ).toThrowError(/toBeEmptyDOMElement\(\)/)
   })
 })

src/to-have-text-content.js

@@ -25,7 +25,7 @@ export function toHaveTextContent(
           '',
         ),
         checkingWithEmptyString
-          ? `Checking with empty string will always match, use .toBeEmpty() instead`
+          ? `Checking with empty string will always match, use .toBeEmptyDOMElement() instead`
           : `Expected element ${to} have text content`,
         checkWith,
         'Received',