Failed to load the web page on all testcafe versions
shyedhu opened this issue · 19 comments
What is your Scenario?
Looks like testcafe tool not working for one of web page and throwing error says “Failed to load the page”
Failed to load the page at "".
Increase the value of the "pageRequestTimeout" variable, enable the "retryTestPages" option, or use quarantine mode to perform additional attempts to execute this test.
You can find troubleshooting information for this issue at "https://go.devexpress.com/TestCafe_FAQ_ARequestHasFailed.aspx".
Error details:
TypeError: ExprGen[itemType] is not a function
What is the Current behavior?
about:error empty screen loading instead of actual web page
What is the Expected behavior?
Web page should load on any browsers with any node version with testcafe tool
What is your public website URL? (or attach your complete example)
none
What is your TestCafe test code?
I’ve send sample POC code to your email: support@devexpress.com , Kindly check and fix as soon as possible
Your complete configuration file
No response
Your complete test report
No response
Screenshots
Steps to Reproduce
- git clone {GIT_URL} repo which sent it to your email: support@devexpress.com
- cd testcafe-poc
- npm install
- npm run test
TestCafe version
Version: 1.19.0
Node.js version
v14.17.0
Command-line arguments
NONE
Browser name(s) and version(s)
Chrome Version 96.0.4664.110
Platform(s) and version(s)
macOS Mojave Version 10.14.6
Other
No response
I am having the same issue. This is really strange because nothing was changed to my knowledge. On April 12th between 11:00a and 11:30a cdt, I started noticing the issue. In the following 2 days it propagated to all ci/cd runs. I have tried upgrading from 1.20.1 on multiple versions and the issue still exists. The only way to get around the issue that I have found is to enable nativeAutomation which is not an acceptable solution because Browserstack is not supported and we are also experiencing different rendering behavior which deems some important button containers un-clickable. My team will have no choice but to move to playwright if these issues are not resolved within a timely manner. Please let me know how I can help. Thanks!
Thanks, @patrickathompson , I am disappointed that testcafe stopped working starting April 12th for only some web pages. My question to support@devexpress.com do we have any updates for the fix.. I'm sure upgrading the testcafe version will not going to help anymore .. I think testcafe's dependencies causing that issue TypeError: ExprGen[itemType] starting April 12th. I can't switch to other automation tools for now since using testcafe for a very long time .. Hopefully, the dev express support team will provide a temporary workaround or fix that problem very soon.
@felis2803 Could you please explain how this is happening behind the scenes?
Does TestCafe tries to download some requirements/ scripts/ something of that sort from browser before every test run? otherwise how can an issue like can float up in my setup where nothing has been updated for months. I have older version of testcafe 2.2.0, even if I assume there is a bug due to recent release how can it get propagated if i have't updated my setup in months?
Please throw some light on this.
Any updates on this? We are also suddenly experiencing a similar issue.
Seems like it is failing because of missing PropertyDefinition and PrivateIdentifier thingies from this PRs
https://github.com/DevExpress/esotope-hammerhead/pull/22/files
https://github.com/DevExpress/esotope-hammerhead/pull/21/files
I checked the value of itemType at the moment of error
Applying those changes using yarn patch has helped me to unblock the pipeline.
Can such kind of issues be avoided in future? I didn't update anything, so I did not expect something to brake
I'm facing the same issue, it's blocking some of our deployment pipelines, I would really appreciate it if it gets prioritized.
Seems like it is failing because of missing PropertyDefinition and PrivateIdentifier thingies from this PRs https://github.com/DevExpress/esotope-hammerhead/pull/22/files https://github.com/DevExpress/esotope-hammerhead/pull/21/files I checked the value of itemType at the moment of error
Applying those changes using yarn patch has helped me to unblock the pipeline.
Can such kind of issues be avoided in future? I didn't update anything, so I did not expect something to brake
@byslavik is there any other way of doing that but with npm?
Is it possible to get the below 2 PRs merged in as they appear to fix the issue?
https://github.com/DevExpress/esotope-hammerhead/pull/22/files
https://github.com/DevExpress/esotope-hammerhead/pull/21/files
yes please merge these 2 PRs, they will fix the issue
https://github.com/DevExpress/esotope-hammerhead/pull/22/files
https://github.com/DevExpress/esotope-hammerhead/pull/21/files
Hello guys,
Thank you for your contribution. We are working on the problem. We will check the pull requests and release a new TestCafe version once we fix the issue.
@felis2803 I'll open a PR soon with the testcases for those two PRs in testcafe-hammerhead (per feedback).
Hello guys,
Thank you for your contribution. We are working on the problem. We will check the pull requests and release a new TestCafe version once we fix the issue.
@felis2803 Does this also include fix for older versions or we need to use the latest version only? Cause I am still using an older version (2.2.0) and seeing the issue there as well.
Hello guys,
Thank you for your contribution. We are working on the problem. We will check the pull requests and release a new TestCafe version once we fix the issue.@felis2803 Does this also include fix for older versions or we need to use the latest version only? Cause I am still using an older version (2.2.0) and seeing the issue there as well.
@vinayvennela That fix will work for older version as well as new version 2.5.0
Hello everyone,
We plan to add the fix to testcafe v2.5.1. While we are preparing it, you can use the release candidate version 2.5.1-rc.1, which includes the fix.
Thanks to @sorin-davidoi for the help.
We have released TestCafe@2.5.1-rc.1. It includes a fix for this issue.
@shyedhu I'm sorry, I have to correct you: the fix won't work for older versions.
@vinayvennela We only maintain one branch where we add all the changes.
Then how come the issue started appearing in older versions all of a sudden?
Probably the website being tested changed - for us it popped up when we changed the transpilation configuration to drop support for some older browser versions (before this private fields were transpiled away).