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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to adjust the default wait time. #438

Closed
98gmarquee opened this issue Oct 3, 2018 · 10 comments
Closed

Ability to adjust the default wait time. #438

98gmarquee opened this issue Oct 3, 2018 · 10 comments

Comments

@98gmarquee
Copy link

馃殌 Feature Proposal

It would be useful to be able to override the default "wait" time. In the old IDE, you could change the default in the settings, but I'm not seeing a way to do that anymore.

Motivation

I usually set it to something really high like 5 minutes or more as we have things that load a database into cache and on large setups, it can take 3+ minutes on the first hit after java is restarted for the site to "open". It's also helpful when there's a web service that is taking over a minute to return data, then the "wait for visible" function doesn't throw an error.

Example

Just something as simple as "set wait time"|300000|" as the first command on a script before "open||" is called.

@sporthcophcop
Copy link

With in a testsuite it is possible to set the implicit wait time.
afbeelding
afbeelding
Or do you want change it dynamically during the run of a script?
The pause command let you wait explicitly in your scripts.

@corevo
Copy link
Member

corevo commented Oct 5, 2018

That is not the implicit wait time, I should probably clarify this in the dialog, this is for the selenium-side-runner, it is the timeout for each test in the suite.
But adding an implicit wait override makes quite a bit of sense there.

@98gmarquee
Copy link
Author

Being able to change it directly in a scripts steps would prove useful. Then if you have to filter through 15 pages, and you have a couple that have things that lag on you, you can increase the wait time for those elements alone, or sections of the script vs using a global for all scripts in a suite. Kind of like the "setSpeed" setting used to let you do which was more to create a static pause between steps.

Setting it globally is fine as well. If that's how it works.

@Yrds
Copy link

Yrds commented Oct 6, 2018

@98gmarquee now you can use "wait" commands in selenium 3.4.0 in that cases

@98gmarquee
Copy link
Author

Yeah, just wish they wouldn't have made the new window popup/open thing as that's really annoying to me.

@ChrisLMerrill
Copy link

I will second the request for changing the default wait timeout. My customer wants to use SeleniumIDE to gather performance data on their system. I've cobbled together some rudimentary performance measurement recording within SeleniumIDE and I am considering writing an extension to make it more elegant. But some of the operations take >30 seconds - which of course kills the test and prevents gathering the data they need. (Yes, they know that 30sec is unacceptable - which is why they want to start tracking changes in performance as they work to improve it)

@steve-hyde
Copy link

Does anyone know how to execute a task at an exact time? I need to take a turn to fast

@toddtarsi
Copy link
Contributor

How exact are we talking here? I'd say for either v3 or v4, you probably want to use the browser.
Something like an executeAsyncScript would work. I believe this would check every 50 ish ms:

new Promise(function(done) => {
  const handler = setInterval(() => {
    if (Date.now() < ${yourTargetTime}) return;
    clearInterval(handler);
    done();
  }, 50);
});

I'm not sure what the exact format is for executeAsyncScript is right now, so trying some stuff out might be necessary. Further, I'm not sure if there is like time zone stuff this has to account for, but its at least decently illustrative.

@toddtarsi
Copy link
Contributor

This exists as a configurable timeout property.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants