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

not respecting .get() timeout #71

Open
midleman opened this issue Aug 24, 2023 · 5 comments
Open

not respecting .get() timeout #71

midleman opened this issue Aug 24, 2023 · 5 comments

Comments

@midleman
Copy link

midleman commented Aug 24, 2023

Using latest version: 1.10.5.

Try this snippet:

    cy.get('thing', { timeout: 10000 })
      .if('visible')
      .log('thing is visible')
      .else()
      .log('thing is not visible')

It should wait 10 seconds for "thing" before deciding which branch to exercise. However, it immediately goes into the else branch.

@midleman
Copy link
Author

I've been poking around trying to make sense of code, and it def seems to be an issue related to "disabling the built-in assertion".

// disable the built-in assertion

@gnsoria
Copy link

gnsoria commented Nov 16, 2023

This is also happening for me. I seem to recall a previous version of cypress-if respecting the timeout, but unfortunately that was at a previous employer so I don't know specifically which versions of cypress and cypress-if we were using. But it's breaking for me on cypress-if@1.10 and cypress-if@1.9. (1.8 is failing before that point for a different reason, so I was unable to confirm on that version.)

@GeorgeXCV
Copy link

Running into the same issue on cypress-if@1.10.5 and cypress@13.6.2

@ederusb2
Copy link

Same problem with cypress@13.6.4 and cypress-if@1.12.0

@galen-at-atomic-jolt
Copy link

Same problem with cypress@13.15 and cypress-if@1.13.0...

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

5 participants