Testcafe-hammerhead: Test Execution hanging and restarting execution as hammerhead keeping assets requests in pending state for long time

[lokender88]

What is your Test Scenario?

Requesting for page url load and added waitForLoad with some expected locator and text visibility. But I still see that some of the assets requests are in pending state for long time in Network console which is initiated by hammer head. Due to this my test are hanging in the middle of somewhere and not moving forward with further steps.

Even I verified same page url manually and all assets requests are loading properly without any issues when we hit same url manually in browser.

Note: Same test scenarios was executing perfectly in Firefox 63.0 browser.

What is the Current behavior?

Test Execution hanging and restarting execution as hammerhead keeping assets requests in pending state for long time

What is the Expected behavior?

Assets request should not keep in pending status.

Screenshots:

Your Environment details:

• testcafe version: 0.23.3-alpha.1 and 0.23.3
• node.js version: v8.12.0
• command-line arguments: testcafe chrome -e mytest.js
• browser name and version: Chrome 70, Safari12
• platform and version: macOS 10.14
• other: same test execution was works fine with Firefox 63 versions.

[miherlosev]

Hi @lokender88

Thank you for the provided details.
Browsers restrict the number of maximum concurrent connections to the same domain. They do it to prevent DDOS attacks. This value is different for different browsers, for example, it equals 6 in Google Chrome, 15 - in Mozilla Firefox.
TestCafe proxies all resources through only 2 channels.
One channel is used for an opened web site and loading its same-domain resources, the other one - for loading all cross-domain resources.
If your web application has a lot of same and cross domain resources, you can see resource load slowdown because TestCafe directs all connections via two points.
In spite of this, your tests should not hang. If during test execution your test pages are loaded 3-4 times more slowly than you load them without TestCafe, this problem can be related to our products. In this case, could you please provide an example in which we can reproduce this behavior?

[lokender88]

hi @miherlosev ,

Thanks for looking into it and providing details.

Yes. The page is loading faster without TestCafe. I noticed that page load is taking longer time due to hammerhead request block for long time. Below is the sample reference url where this issue reproducible.

URL

Please let me know if you need any more information.

[miherlosev]

I got the 'Access Denied' error on access to the provided url.

Should I anything set up before accessing to the url?

[lokender88]

It is a public url to access from anywhere. Please try this URL.

[lokender88]

@miherlosev Did you get a chance to look into it?

[AndreyBelym]

We still can't access your site because of the 'Acess Denied` error.

[jensbodal]

Just want to add that I can access the URL and am not receiving 'Access Denied'. I have no affiliation with this github issue I'm just doing some research on a different issue.

[lokender88]

@AndreyBelym / @miherlosev , Please try with URL.

If still not accessible, please let me know the country name you are trying to access it. So I can find the way to access it.

[AndreyBelym]

Thank you for providing this URL, it works and I've reproduced the problem.

I guess something breaks page resource processing in the testcafe-hammerhead proxy because I can reproduce it without TestCafe in the testcafe-hammerhead playground.

[lokender88]

@AndreyBelym & Team, Did we find the solution for it?. Can we prioritize this as it's blocking cross browser test executions?.

[LavrovArtem]

@lokender88, We need additional time to investigate this problem. After that, we'll add it to the current sprint.

[Avinger27]

@lokender88 @AndreyBelym Ran into this problem today. I can workaround this for now, but has this been resolved?

[miherlosev]

@lokender88
The problem has been fixed in the [email protected] version.
 
@Avinger27
It looks like a separate issue. Please try to run your tests using the latest TestCafe version (1.1.3).
If the problem still persists, please provide a simple example where we can reproduce the problem on our side.

[lock[bot]]

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.