fix(error-messages): issue: Output User Error instead of New Issue er…

…ror for wrong node from user

 - by adding additional check and correct error-message according to edge use case from the issue testing-library#911

src/__tests__/helpers.js

@@ -15,7 +15,7 @@ describe('window retrieval throws when given something other than a node', () =>
   // actually here should be another more clear error output
   test('screen as node', () => {
     expect(() => getWindowFromNode(screen)).toThrowErrorMatchingInlineSnapshot(
-      `"Unable to find the \\"window\\" object for the given node. Please file an issue with the code that's causing you to see this error: https://github.com/testing-library/dom-testing-library/issues/new"`,
+      `"It looks like you used 'screen' object instead of one of selectors from screen.selectMethod and it passed a 'screen' instead of a DOM node. Did you do something like \`fireEvent.click(screen, ...\` when you meant to use a \`fireEvent.click(screen.getBy..., \`?"`,
     )
   })
   test('Promise as node', () => {

src/helpers.js

@@ -105,6 +105,13 @@ function getWindowFromNode(node) {
     throw new Error(
       `It looks like you passed an Array instead of a DOM node. Did you do something like \`fireEvent.click(screen.getAllBy...\` when you meant to use a \`getBy\` query \`fireEvent.click(screen.getBy...\`?`,
     )
+  } else if (
+    node.debug instanceof Function &&
+    node.logTestingPlaygroundURL instanceof Function
+  ) {
+    throw new Error(
+      `It looks like you used 'screen' object instead of one of selectors from screen.selectMethod and it passed a 'screen' instead of a DOM node. Did you do something like \`fireEvent.click(screen, ...\` when you meant to use a \`fireEvent.click(screen.getBy..., \`?`,
+    )
   } else {
     // The user passed something unusual to a calling function
     throw new Error(