pageRequestTimeout. Specifies the time in milliseconds to wait for the HTML page. If TestCafe does not receive the page within the specified time, an error will be thrown.
The documentation is still unclear to me. What exactly is testcafe waiting for?
Test Cafe: 2.5.0 Node: v16.19.0 Browser: chrome
I'm having trouble expressing and trying to figure out the exact cause.
Failed to load the page at "https://xxx/".
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:
Failed to complete a request to "https://xxx/" within the timeout period. The problem may be related to local machine's network or firewall settings, server outage, or network problems that make the server inaccessible.
pageRequestTimeout is 30000 and isolation mode is on. What's happening is that the website is loading and after a timeout testcafe just redirects me to a blank "about:error" page. The website can be opened manually.
P粉3511384622024-03-20 15:31:07
The pageRequestTimeout option in TestCafe specifies the duration, in milliseconds, that TestCafe waits for an HTML page to load before timing out and throwing an error. In your case, it seems that TestCafe is unable to load the page at the specified URL within the 30 second timeout and therefore throws an error.
The error message indicates that the problem may be related to the local computer's network or firewall settings, a server outage, or a network problem that renders the server inaccessible. The page you are trying to load might be taking longer to load due to network or server issues, or your local computer's firewall settings are preventing the page from loading.
To resolve this issue, you can try increasing the value of the pageRequestTimeout option, enabling the retryTestPages option, or performing other attempts to perform the test using isolation mode. You can also try accessing the page manually to check if it loads correctly and if there are any network or firewall issues on your computer.