Bayheck
commented
1 month ago Hello,
That is not a bug.
Testcafe still uses testcafe-hammerhead even in native automation mode.
In native automation, we replaced the URL rewriting and event emulation submodules from hammerhead, but it still has components that Testcafe uses. See more details in our documentation:
Thank you for reaching out.
What is your Scenario?
Launch an application in Native mode, Check the network logs. I can see hammer head is listed in the logs.
What is the Current behavior?
Hammerhead is listed in network logs
What is the Expected behavior?
Hammerhead should not be used in native mode.
What is the public URL of the test page? (attach your complete example)
testcafe edge,chrome -e test.js
What is your TestCafe test code?
Launch an application in Native mode, Check the network logs. I can see hammer head is listed in the logs.
Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce
Launch an application in Native mode, Check the network logs. I can see hammer head is listed in the logs.
TestCafe version
3.6.0
Node.js version
No response
Command-line arguments
testcafe edge,chrome -e test.js
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response