DevExpress / testcafe-hammerhead

A powerful web-proxy used as a core for the TestCafe testing framework. :hammer: :smiley:
https://testcafe.io
MIT License
171 stars 162 forks source link

TestCafe not rendering header of the page, printing 'App not found.' message in console instead. #2871

Closed aarti315 closed 1 year ago

aarti315 commented 1 year ago

What is your Scenario?

TestCafe Azure DevOps pipeline which is running approx 120 cases daily since more than 6 months started failing more than 35+ TestCases since last few days.

What is the Current behavior?

35+ Testcases are failing as page header is not getting loaded. and in console we see message 'App not found'.

What is the Expected behavior?

Page should load fine with header and TestCase should run fine without failing

What is your public website URL? (or attach your complete example)

NA right now as can not share private details.

We need to understand in what scenario hammerhead would print 'App not found' message.

What is your TestCafe test code?

Not available

Your complete configuration file

NA

Your complete test report

No response

Screenshots

No response

Steps to Reproduce

  1. NA

TestCafe version

2.4.0

Node.js version

19.7.0

Command-line arguments

testcafe chrome:headless SmokeTest/*/ -q -e --concurrency 2 --disable-http2

Browser name(s) and version(s)

No response

Platform(s) and version(s)

No response

Other

No response

AlexKamaev commented 1 year ago

It is unlikely that the "App not found" message comes from testcafe or testcafe-hammerhead. Unfortunately, we cannot say more without a working example that demonstrates the issue. I can only recommend you to try to run your tests in proxyless mode, which was developed especially to replace some testcafe-hammerhead features to make tests more stable.

See this article for details: https://testcafe.io/documentation/404237/guides/experimental-capabilities/proxyless-mode

github-actions[bot] commented 1 year 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.