Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to set pageLoadTimeout using Continuous Integration #2023

Closed
GoshaFighten opened this issue Dec 22, 2017 · 2 comments
Closed

How to set pageLoadTimeout using Continuous Integration #2023

GoshaFighten opened this issue Dec 22, 2017 · 2 comments
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot.

Comments

@GoshaFighten
Copy link

Is there a way to set the pageLoadTimeout value using the npm installation method?

I would like to use the pageLoadTimeout parameter defined here http://devexpress.github.io/testcafe/documentation/using-testcafe/programming-interface/runner.html#run

Our tests are failing because they don't wait long enough for the page t
o load, so I want to set a timeout at a global level. I know that there is a .wait() function, but I that is not global so I would have to add it to every page load of every test, which I don't want to do.

The code I am using is attached
WarmupTests.js.txt

@GoshaFighten
Copy link
Author

I've checked this case again and see that you wish to have an option in our paid TestCafe, which is a counterpart of the pageLoadTimeout option in our new free TestCafe. The former TestCafe does not have this option. If you don't need to use our Recorder, I suggest you switch to our new free TestCafe. If you need it, use the old TestCafe and the wait method.

@lock
Copy link

lock bot commented Mar 28, 2019

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.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot.
Projects
None yet
Development

No branches or pull requests

1 participant