DevExpress / testcafe

A Node.js tool to automate end-to-end web testing.
https://testcafe.io
MIT License
9.82k stars 671 forks source link

"Uncaugt object" error after upgrade #8266

Closed ejerskov closed 1 month ago

ejerskov commented 1 month ago

What is your Scenario?

I just upgraded my testcafe version from 3.2.0 to 3.6.2 and I suddenly get these Uncaught Object errors.

What is the Current behavior?

After 1 loop it throws an error

What is the Expected behavior?

Expected to continue through out the loop

What is the public URL of the test page? (attach your complete example)

No public url

What is your TestCafe test code?

The first run through is OK but on the second run through it fails.

const secondLevelCategories = await Selector(selectors.sparePartPage.listViewCategories).count;

//Loop through second level categories
for (let k = 0; k < secondLevelCategories; k++) {
  //Click category
  await t.click(Selector(selectors.sparePartPage.listViewCategories).nth(k))
}

Error:

1) Uncaught object

   "{"callsite":{"filename":"/tests/02_spare_parts_page.tests.ts","lineNum":172,"callsiteFrameIdx":5,"stackFrames":[{},{},{},{},{},{},{},{},{}],"isV8Frames":true}}"
      was thrown. Throw Error instead.

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

1. 2. 3.

TestCafe version

3.6.2

Node.js version

No response

Command-line arguments

testcafe chrome ./tests

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

No response

github-actions[bot] commented 1 month ago

Thank you for submitting a bug report. We would love to help you investigate the issue. Please share a simple code example that reliably reproduces the bug. For more information, read the following article: How To Create a Minimal Working Example When You Submit an Issue. We look forward to your response.

github-actions[bot] commented 1 month ago

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.