https://cypress.io logo
Join Discord
Powered by
# e2e-testing
  • m
    You are amazing 🙂 Thank you!
  • t
    im trying to reach an input that is nested inside of 2 iframes. (not able to change touch that code) Cy seems to be able to find the second iframe inside the first one, however the input is not accessible via .find(). Thinking it might be selectors i 3x checked them. (using input[tpye=tel] just to see if it works atm) Not sure how to approach this issue, would love some help. Let me know if there is any further information I can provide, (im prty new to this).
  • m
    Can you please share the piece of code you are using to retrieve that element? You can obfuscate the ids/names.
  • t
    ty, hope it helps
  • t
    the cy.iframe is provided by the npm package "cypress-iframe"
  • p
    are the iframes in the same domain? Cypress currently doesn't support cross domain iframes (something that i dont like at all)
  • m
    It already does. Please check

    https://www.youtube.com/watch?v=XMJP07Ft1nA&list=PLP9o9QNnQuAYYRpJzDNWpeuOVTwxmIxcI&index=2&ab_channel=glebbahmutov▾

  • m
    I think you should use cy.get() for the field you would like to pass input to.
    t
    p
    e
    • 4
    • 36
  • g
    hi, how to call async function in a custom cypress command? I did something like this:
    Copy code
    ts
Cypress.Commands.add('foo', () => {
  Cypress.log('foo', ...)
  return someLoginFunctionWithHTTPCall()
})
    When I call this method 
    cy.foo()
    , the network call is made successfully, but cypress is "stuck", it wont go to the next step
  • m
  • m
    There is no async in Cypress. Cypress has a declarative chaining syntax that pipes inputs and outputs. Most of the time, you do not even need to deal with the values going through the chain. Async/await makes it much easier to unwrap values, but Commands are not Promises, using await on a Cypress chain will not work as expected. This is a very conscious and important design decision that gives Cypress a fluid, functional programming inspired, observable-stream-like api that many begin to prefer over what they have been used to.
  • m
    Can't he use cy.intercept() and cy.wait()?
  • m
    it might be as easy as Cypress.Commands.add('foo', () => { cy.log('foo', ...) return someLoginFunctionWithHTTPCall() })
  • g
    well I believe it's more related to the network call, if I change to :
    Copy code
    ts
Cypress.Commands.add('foo', async () => {
  Cypress.log('foo', ...)
  await someLoginFunctionWithHTTPCall()
  Cypress.log('done', ...)
})
    done
    is not displayed, so we could believe that the issue is because of my custom function the thing is my 
    someLoginFunctionWithHTTPCall
    is 
    firebase.signInWithEmailAndPassword
  • m
    no await
  • m
    try this
  • m
    Cypress.Commands.add('foo', () => { cy.log('foo', ...) cy.someLoginFunctionWithHTTPCall() cy.log('done') })
  • m
    you can try that middle fn as a fn vs command
  • g
    I would move my firebase call in its own command:
    Copy code
    ts
Cypress.Commands.add('firebaseLogin',  () => {
  return firebase.signIn(...)
})
    and call the command from another one?
    Copy code
    ts
Cypress.Commands.add('login',  () => {
  return cy.firebaseLogin()
})
  • m
    should be perfectly fine
  • m
    you might find working examples that apply to what you want here https://github.com/muratkeremozcan/cypress-crud-api-test
  • m
    lots of log examples there
  • g
    I'll test, but I cannot understand why it would work this way, rather than having one command that would call my firebase fn 🤔
  • g
    thanks for the help tho
  • g
    it's still stuck on that login call command, even if the HTTP call is successful I give up for today, will check this tomorrow! thanks again for your help 👍
  • m
    if you have a sample repo to share, we could just pull it, and help you make it work
  • g
    you're right that would be simpler, I'll try to make one when I have time
  • g
    well, of course when I try to replicate my issue, I do not have it anymore and it works without any issue, nice i am doomed when it comes to work with cypress
  • m
    it's like going to the doctor and they tell you everything is fine the way I go about anything is to try to first make it work in a stupid simple example, then replicate that internally where there may be many factors and gotchas impacting it that simple example, the control group, will always help compare & contrast for the purpose of getting to bottom of a failure
  • r
    I get type errors when doing something like cy.get('[name="email"]'.type(Cypress.config('paidUsername')) How can I use Cypress.config in this way with TypeScript?
1...404142...192Latest