Inspected target navigated or closed

[vasilyevi]

What is your Scenario?

After upgrading to 3.6.0 the issue happens randomly, the same code might work multiple time, but 1-3 of of 10 run could be failed

What is the Current behavior?

Unhandled promise rejection:

ERROR 'Error: Inspected target navigated or closed
at /home/runner/test/src/js/tests/node_modules/chrome-remote-interface/lib/chrome.js:94:35
at Chrome._handleMessage (/home/runner/test/src/js/tests/node_modules/chrome-remote-interface/lib/chrome.js:272:17)
at WebSocket. (/home/runner/test/src/js/tests/node_modules/chrome-remote-interface/lib/chrome.js:240:22)
at WebSocket.emit (node:events:517:28)
at WebSocket.emit (node:domain:489:12)
at Receiver.receiverOnMessage (/home/runner/test/src/js/tests/node_modules/ws/lib/websocket.js:1068:20)
at Receiver.emit (node:events:517:28)
at Receiver.emit (node:domain:489:12)
at Receiver.dataMessage (/home/runner/test/src/js/tests/node_modules/ws/lib/receiver.js:517:14)
at Receiver.getData (/home/runner/test/src/js/tests/node_modules/ws/lib/receiver.js:435:17)

What is the Expected behavior?

N/A

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

N/A

What is your TestCafe test code?

N/A

Your complete configuration file

No response

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

N/A

TestCafe version

3.6.0

Node.js version

v18.19.1

Command-line arguments

npx testcafe

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

No response

[github-actions]

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.

[vasilyevi]

As I wrote, unfortunately I do not have exact steps to be able to stable reproduce the issue, happens just randomly and not too often, so cannot provide exact sample. Maybe stacktrace might give you some ideas...

[vasilyevi]

few more things. As far as I can see it always happens as Unhandled promise rejection . Actually, everytime it happens the test itself is completed, so it performs all the steps from the beginning to the end. But on after step const hasErr = !!t.testRun.errs.length; returns true.
Sometimes it happens in before hook, sometimes during the test itself, but always it completes all the steps and fail the test in after hook because it says that this is an error.

Do you have any testcafe logs or something which might give more details?

[Bayheck]

Hello,

Unfortunately, without a minimal working example, we cannot determine the cause of this issue.

[vasilyevi]

So, there is no any testcafe logs or somehting?

[Bayheck]

Hello,

You can try to enable TestCafe logs on your CI - set DEBUG=testcafe:*,hammerhead:*.

[vasilyevi]

Where to set? is it env var?

[vasilyevi]

Would that work with native automation?

[Bayheck]

Yes, it is an environment variable, and it works with native automation.

To enable the debug log, you can use the following way:

set DEBUG=testcafe:*,hammerhead:*
testcafe chrome index.js 2> testcafe.log

Before running TestCafe, you need to set the DEBUG environment variable like in the example above.
Then, you need to run TestCafe and redirect the output to the file.

Please refer to the following help topic for details: https://testcafe.io/documentation/402636/faq/general-info#related-questions.