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

Wait timeout value does not work #1832

Open
steveshearer opened this issue May 16, 2024 · 1 comment
Open

Wait timeout value does not work #1832

steveshearer opened this issue May 16, 2024 · 1 comment

Comments

@steveshearer
Copy link

馃悰 Bug Report

A clear and concise description of what the bug is.

To Reproduce

I am using the Chrome extension version of Selenium IDE v 3.17.2

I have the following command as one of my tests because other actions have to happen before moving on, and I need a longer timeout value.
Command wait for text
Target css=.ant-btn > span
Value 3600000.0

I have tried several of the other wait variants with the same issues too

Expected behavior

I am expecting the test to wait while I perform the other actions and the text appears. However it seems to always timeout after (I think) 30 seconds, regardless of what value I put in the command.

Project file reproducing this issue (highly encouraged)

Please provide a project file .side that reproduces this issue. I'm really sorry, I have tried to attach the file several times but I cant seem to get that to work. I get the message "We don't support that file type."

Issues without a reproduction project are likely to stall.

Environment

OS: Windows 10
Selenium IDE Version: 3.17.2
Selenium SIDE Runner Version:
Node version:
Browser: Chrome
Browser Version: not sure where to find the version - but it is a recent one

@toddtarsi
Copy link
Contributor

@steveshearer - Yeah, this is a limitation of waitForText. It only has two argument spots, one for css selector, and one for matching text. As a result, there isn't a third argument for timeout. At some point, I'd like to move timeout off of the main command arguments and instead make it its own flag, as modern test runners tend to basically just poll everything for a time range nearly.

I am not really fixing v3, but I assure you that in v4, all of the timeouts (except waitForText) work fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants