Update snapshots

Author: eps1lon

src/__tests__/element-queries.js

@@ -37,6 +37,7 @@ test('get throws a useful error message', () => {
     .toThrowErrorMatchingInlineSnapshot(`
 "Unable to find a label with the text of: LucyRicardo
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
@@ -45,34 +46,39 @@ test('get throws a useful error message', () => {
     .toThrowErrorMatchingInlineSnapshot(`
 "Unable to find an element with the placeholder text of: LucyRicardo
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
 `)
   expect(() => getByText('LucyRicardo')).toThrowErrorMatchingInlineSnapshot(`
 "Unable to find an element with the text: LucyRicardo. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
 `)
   expect(() => getByTestId('LucyRicardo')).toThrowErrorMatchingInlineSnapshot(`
 "Unable to find an element by: [data-testid="LucyRicardo"]
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
 `)
   expect(() => getByAltText('LucyRicardo')).toThrowErrorMatchingInlineSnapshot(`
 "Unable to find an element with the alt text: LucyRicardo
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
 `)
   expect(() => getByTitle('LucyRicardo')).toThrowErrorMatchingInlineSnapshot(`
 "Unable to find an element with the title: LucyRicardo.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
@@ -81,6 +87,7 @@ test('get throws a useful error message', () => {
     .toThrowErrorMatchingInlineSnapshot(`
 "Unable to find an element with the display value: LucyRicardo.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
@@ -90,6 +97,7 @@ test('get throws a useful error message', () => {
 
 There are no accessible roles. But there might be some inaccessible roles. If you wish to access them, then set the \`hidden\` option to \`true\`. Learn more about this here: https://testing-library.com/docs/dom-testing-library/api-queries#byrole
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
@@ -354,6 +362,7 @@ test('label with no form control', () => {
   expect(() => getByLabelText(/alone/)).toThrowErrorMatchingInlineSnapshot(`
 "Found a label with the text of: /alone/, however no form control was found associated to that label. Make sure you're using the "for" attribute or "aria-labelledby" attribute correctly.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <label>
     All alone
@@ -371,6 +380,7 @@ test('label with "for" attribute but no form control and fuzzy matcher', () => {
     .toThrowErrorMatchingInlineSnapshot(`
 "Found a label with the text of: alone, however no form control was found associated to that label. Make sure you're using the "for" attribute or "aria-labelledby" attribute correctly.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <label
     for="foo"
@@ -393,6 +403,7 @@ test('label with children with no form control', () => {
     .toThrowErrorMatchingInlineSnapshot(`
 "Found a label with the text of: /alone/, however no form control was found associated to that label. Make sure you're using the "for" attribute or "aria-labelledby" attribute correctly.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   
   
@@ -433,6 +444,7 @@ test('label with non-labellable element', () => {
   expect(() => getByLabelText(/Label/)).toThrowErrorMatchingInlineSnapshot(`
 "Found a label with the text of: /Label/, however the element associated with this label (<div />) is non-labellable [https://html.spec.whatwg.org/multipage/forms.html#category-label]. If you really need to label a <div />, you can use aria-label or aria-labelledby instead.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   
   
@@ -482,6 +494,7 @@ test('multiple labels with non-labellable elements', () => {
 
 Found a label with the text of: /Label/, however the element associated with this label (<p />) is non-labellable [https://html.spec.whatwg.org/multipage/forms.html#category-label]. If you really need to label a <p />, you can use aria-label or aria-labelledby instead.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   
   
@@ -533,6 +546,7 @@ test('totally empty label', () => {
   expect(() => getByLabelText('')).toThrowErrorMatchingInlineSnapshot(`
 "Found a label with the text of: , however no form control was found associated to that label. Make sure you're using the "for" attribute or "aria-labelledby" attribute correctly.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <label />
 </div>"
@@ -1221,6 +1235,7 @@ test('return a proper error message when no label is found and there is an aria-
     .toThrowErrorMatchingInlineSnapshot(`
 "Unable to find a label with the text of: LucyRicardo
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <input
     aria-labelledby="not-existing-label"

src/__tests__/role.js

@@ -16,6 +16,7 @@ Here are the accessible roles:
 
   --------------------------------------------------
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <h1>
     Hi
@@ -39,6 +40,7 @@ Here are the available roles:
 
   --------------------------------------------------
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div
     hidden=""
@@ -58,6 +60,7 @@ test('logs error when there are no accessible roles', () => {
 
 There are no accessible roles. But there might be some inaccessible roles. If you wish to access them, then set the \`hidden\` option to \`true\`. Learn more about this here: https://testing-library.com/docs/dom-testing-library/api-queries#byrole
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
@@ -72,6 +75,7 @@ test('logs a different error if inaccessible roles should be included', () => {
 
 There are no available roles.
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div />
 </div>"
@@ -86,6 +90,7 @@ test('by default excludes elements that have the html hidden attribute or any of
 
 There are no accessible roles. But there might be some inaccessible roles. If you wish to access them, then set the \`hidden\` option to \`true\`. Learn more about this here: https://testing-library.com/docs/dom-testing-library/api-queries#byrole
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div
     hidden=""
@@ -106,6 +111,7 @@ test('by default excludes elements which have display: none or any of their pare
 
 There are no accessible roles. But there might be some inaccessible roles. If you wish to access them, then set the \`hidden\` option to \`true\`. Learn more about this here: https://testing-library.com/docs/dom-testing-library/api-queries#byrole
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div
     style="display: none;"
@@ -128,6 +134,7 @@ test('by default excludes elements which have visibility hidden', () => {
 
 There are no accessible roles. But there might be some inaccessible roles. If you wish to access them, then set the \`hidden\` option to \`true\`. Learn more about this here: https://testing-library.com/docs/dom-testing-library/api-queries#byrole
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div>
     <ul
@@ -152,6 +159,7 @@ test('by default excludes elements which have aria-hidden="true" or any of their
 
 There are no accessible roles. But there might be some inaccessible roles. If you wish to access them, then set the \`hidden\` option to \`true\`. Learn more about this here: https://testing-library.com/docs/dom-testing-library/api-queries#byrole
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <div
     aria-hidden="true"
@@ -241,6 +249,7 @@ Here are the accessible roles:
 
   --------------------------------------------------
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <h1>
     Sign 
@@ -287,6 +296,7 @@ Here are the accessible roles:
 
   --------------------------------------------------
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <h1>
     Sign 
@@ -310,6 +320,7 @@ Here are the accessible roles:
 
   --------------------------------------------------
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <h1>
     Sign 
@@ -337,6 +348,7 @@ Here are the accessible roles:
 
   --------------------------------------------------
 
+Ignored nodes: comments, <script />, <style />
 <ul>
   <li />
 </ul>"
@@ -371,6 +383,7 @@ Here are the accessible roles:
 
   --------------------------------------------------
 
+Ignored nodes: comments, <script />, <style />
 <body>
   <button
     aria-label="my-tab"
@@ -394,20 +407,24 @@ test('accessible regex name in error message for multiple found', () => {
 
 Here are the matching elements:
 
+Ignored nodes: comments, <script />, <style />
 <button>
   Increment value
 </button>
 
+Ignored nodes: comments, <script />, <style />
 <button>
   Decrement value
 </button>
 
+Ignored nodes: comments, <script />, <style />
 <button>
   Reset value
 </button>
 
 (If this is intentional, then use the \`*AllBy*\` variant of the query (like \`queryAllByText\`, \`getAllByText\`, or \`findAllByText\`)).
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <button>
     Increment value
@@ -436,20 +453,24 @@ test('accessible string name in error message for multiple found', () => {
 
 Here are the matching elements:
 
+Ignored nodes: comments, <script />, <style />
 <button>
   Submit
 </button>
 
+Ignored nodes: comments, <script />, <style />
 <button>
   Submit
 </button>
 
+Ignored nodes: comments, <script />, <style />
 <button>
   Submit
 </button>
 
 (If this is intentional, then use the \`*AllBy*\` variant of the query (like \`queryAllByText\`, \`getAllByText\`, or \`findAllByText\`)).
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <button>
     Submit
@@ -479,16 +500,19 @@ test('matching elements in error for multiple found', () => {
 
 Here are the matching elements:
 
+Ignored nodes: comments, <script />, <style />
 <button>
   Increment value
 </button>
 
+Ignored nodes: comments, <script />, <style />
 <button>
   Reset value
 </button>
 
 (If this is intentional, then use the \`*AllBy*\` variant of the query (like \`queryAllByText\`, \`getAllByText\`, or \`findAllByText\`)).
 
+Ignored nodes: comments, <script />, <style />
 <div>
   <button>
     Increment value

src/__tests__/suggestions.js

@@ -111,6 +111,7 @@ test('should suggest getByRole when used with getBy', () => {
 getByRole('button', { name: /submit/i })
 
 
+Ignored nodes: comments, <script />, <style />
 <body>
   <button
     data-testid="foo"
@@ -132,6 +133,7 @@ test('should suggest getAllByRole when used with getAllByTestId', () => {
 getAllByRole('button', { name: /submit/i })
 
 
+Ignored nodes: comments, <script />, <style />
 <body>
   
     

src/__tests__/wait-for.js

@@ -123,6 +123,7 @@ test('timeout logs a pretty DOM', async () => {
   expect(error.message).toMatchInlineSnapshot(`
     "always throws
 
+    Ignored nodes: comments, <script />, <style />
     <html>
       <head />
       <body>
@@ -186,6 +187,7 @@ test('when a promise is returned, if that is not resolved within the timeout, th
   expect((await waitForError).message).toMatchInlineSnapshot(`
     "Timed out in waitFor.
 
+    Ignored nodes: comments, <script />, <style />
     <html>
       <head />
       <body />