https://cypress.io logo
Join DiscordCommunities
Powered by
# e2e-testing
  • n
    the logs above are from the testRunner. you can see that the timeout value is a large value, nonetheless, the execution happens immediately
  • n
    below are logs from the app running normally
  • n
    i forget to mention... the cypress version is 6.8.0
  • n
    i updated to 7.3.0. the behavior is the same.
  • a
    hey guys, im running e2e tests locally and are all passing successfully, but when they are executing via github actions, its not able to find in a select box. has anyone else had this problem?
  • a
    here is the error
  • n
    the options are feed with data from an async request? if so, maybe the timeout is reached before the request is completed.
  • a
    no, they are actually hard coded options
  • a
    i tried to wait, too.. just in case something wasnt rendering quickly enough
  • a
    no luck so far
  • n
    that's hard. sorry can't help more.
  • a
    no problem thanks anyway!
  • s
    @User try checking the video logs to see what's going on
  • n
    friends, forget about this. the problem is that large timeout numbers make setTimeout imediatly execute without any error or warning. so our user test tokens (which have many decades of expiration) trigger this odd behavior. tks.
  • s
    np
  • a
    @User Maybe a silly question but I am not sure how to actually view those videos that are created when the tests are run via github actions
  • a
    i do see that it was created
  • s
  • m
    Specific code coverage guides for various stacks is on the roadmap of the team. We already have nifty packages for handling React, so showing the way with Vue (and Nuxt) would be the next logical thing to prioritize. Requests like yours helps us prioritize these things.
  • g
    Cody, the 
    window.nuxtApp.$auth.loginWith('login', data)
    is probably a promise-returning operation? When do you know it is finished? If it returns a promise, then you should return it too from 
    .then
    callback. That way Cypress would know and wait
  • f
    This pointed me in the right direction. thank you. The command ended up looking like:
    Copy code
    js
Cypress.Commands.add('login', () => {
  const data = {
    username: Cypress.env('TEST_USERNAME'),
    password: Cypress.env('TEST_USER_PASSWORD'),
  }
  cy.window().then((window) => {
    return window.nuxtApp.$auth.loginWith('login', { data })
  })
})
    And I use it like:
    Copy code
    js
cy.login().then(() => {})
  • g
    why the 
    .then(() => {})
    ? Why the empty callback after login?
  • i
    Path is already in the details 😂
  • a
    Yeah i see the path. But I cannot access it.
  • i
    That’s strange. Then no idea
  • f
    Sorry, the empty callback is just an example. I place the cy.visit logic within it or anything else I may need.
  • g
    you don't even need it. Since cy.login custom command properly waits now for the nuxtApp action, the rest of the test will wait for cy.login() to finish. So you can simply write
    Copy code
    cy.login()
cy.visit('/')
  • f
    Ah, interesting. This does work. Thank you.
  • f
    Messing around with 
    cy.intercept
    and got a couple of questions (hope you don't mind). What is the best practice to test that the interception did happen? (right now I'm doing the assertion within the interception)
  • s
    An assertion within the interception is fine. Are you just asserting the interception to make sure you implemented it correctly?
1...567...192Latest