https://cypress.io logo
Join DiscordCommunities
Powered by
# general-chat
  • t
    Not sure what you specifically want to test but there is the kitchen sink example website (https://example.cypress.io/) for demonstration purposes. You can also fork and adapt this to your needs: https://github.com/cypress-io/cypress-example-kitchensink
  • a
    how can I check for the result of how many elements the cy.find() returns ?
  • a
    this information is missing on the API
  • t
    That should be logged in the command log and the console output: https://docs.cypress.io/api/commands/find#Command-Log
  • g
  • g
    cy.().find(...).its('length')
    gives you the immediate number, but you probably want to assert something like 
    cy.get().find(...).should('have.length.greaterThan', 10).its('length').then(n => ...)
  • b
    Hi guys! Good morning, how you all doing?
  • b
    I am migrating cypress from the 9.7 to 12.0 version, and Cookies.preserveOnce is deprecated and was removed. In order to use the session, how should I map my previous implementation to the current one? previously I had: cy.Cookies.preserveOnce('session_id', 'cookie1', 'cookie2', 'cookie3', 'cookie4', 'token')
  • b
    I can't find correct documentation on direct mapping between previous implementation for the new one
  • g
  • b
    I can't install these independant packages on my project :/
  • b
    I've also tried this out, it works, but I can't deliver with this package
  • f
    In that case, why not use 
    cy.session()
    ? That's what the previous cookie api was deprecated in favour of
  • b
    for instance, here in the doc for the migration (https://docs.cypress.io/guides/references/migration-guide#Command-Cypress-API-Changes) we have this:
  • b
    but I can't understand how the mappings of "remember_token" and "session_id" are done
  • b
    Neither the property cacheAcrossSpecs exists...
  • b
    so how do I map from this: cy.Cookies.preserveOnce('session_id', 'cookie1', 'cookie2', 'cookie3', 'cookie4', 'token') to cy.session() ?
  • a
    @gray-kilobyte-89541 not really helpful I mean... how hard can it be to press a button and then wait 2 secs as long as there is buttons ?
  • a
    really frustrating
  • a
    every time I press a button... there will be an call to the BE to delete something... after its deleted it will update the list and another delete button should be pressed until no more delete buttons are available... this seams quite impossible to do in a way that works reliably
  • a
    it sounds simple when you describe it... yet its so hard to do
  • f
    The docs explain it pretty clearly. Session takes care of all the cookies without having to specify https://docs.cypress.io/api/commands/session#Syntax
  • g
    what is not helpful? I mean your question is literally what these examples show. Ok, if you want "how hard is it to press a button and then wait 2 secs as long as there is buttons" is 1 liner hard 
    cy.get('button').click().should('not.exist')
  • i
    Hi there! Is it possible to make #958013993425960971 and #971437044163289188 to announcements channel type, so we can follow it from other servers? 👀
  • l
    A few pointers... 1. In the Test Runner you can review the results of any Cypress command by clicking it in the log, then looking at the Console output in the Dev Tools window. (Example here: https://docs.cypress.io/api/commands/find#Command-Log) 2. If your command returned multiple results, you can use 
    .eq(x)
    to pick one by index, or you can use 
    .each()
    to iterate over each of them. So here's an example for you:
    Copy code
    js
cy.get('.button').find('.blueBorder').each(($el) => {
  cy.wrap($el).click()
})
  • l
    > there will be an call to the BE to delete something... after its deleted it will update the list and another delete button should be pressed until no more delete buttons are available Also, if you want to wait for the list to update there are a number of tricks you can do, but they are all dependent on your unique situation. I'm suspecting you could probably make use of 
    cy.intercept()
    in this case. Something like this...
    Copy code
    js
cy.intercept('yourXhrCallToDeleteARow').as('delete')
cy.get('.button').find('.blueBorder').each(($el) => {
  cy.wrap($el).click()
  cy.wait('@delete')
})
  • g
    Read my blog post "Run Just The Failed Tests In Cypress" https://glebbahmutov.com/blog/run-failed-tests/
  • a
    Hi Everyone, any idea why I am NOT seeing at which line my code failed? after Cypress 12 migration the debug line its not displayed anymore and its not easy anymore to find the line where it failed👀
  • a
    this is how it used to be displayed before migrating to cy 12, which was really easy to find the issue
  • i
    @gray-kilobyte-89541 perfect this was very helpful Thank you you rock 🙂
1...101102103...127Latest