https://cypress.io logo
Join Discord
Powered by
# e2e-testing
  • r
    That is probably not the real issue - it pops up 100% of the time whether tests pass or fail.
  • r
    We have an issue to silence it, since it's unrelated and confuses people.
  • r
    Just noise from Electron when run in a docker container.
  • b
    Hi
  • b
    Anyone having idea to mock websocket response in angular app
  • p
    Hi, I have some troubles with button status so I want to ask: How to distinguish enabled and toggled button?
  • p
    while for me 1 is "enabled" and 2 is "disabled", Cypress sees them all as disabled or enabled in terms of being clickable
  • p
    with "should(be.disabled)" Cypress checks if button is clickable, if it isn't outgreyed, in this case both 3 and 4 are disabled
  • p
    is there any command like should(be.toggled)?
  • w
    It depends what the implementation of these buttons is. Can you share the code? Sometime under the hood these rely on checkboxes, sometimes it’s a button with role “switch”. Depending on the implementation, you can use attributes like “checked”, “aria-checked” etc to know if the switch is “on” or “off”.
  • p
    Thanks for your help!
  • p
    based on what you said, I can use this button's role and "aria-checked" attribute
  • p
    how exactly can I do that?
  • p
    cy.get(x).should('have.attr', 'aria-checked="false"') will be ok?
  • g
  • p
    Thank you very much! :)
  • e
    Hello I am trying to disable command log in headless mode (Windows) using CYPRESS_NO_COMMAND_LOG=1 npx cypress run and I get this error CYPRESS_NO_COMMAND_LOG=1 : The term 'CYPRESS_NO_COMMAND_LOG=1' is not recognized as the name of a cmdlet, function, script file, or operable program I also tried passing this parameter as env variable using --env and updating cypress.json, but doesn't seem to work in either case Any pointers on correct usage of this flag to suppress logs would be very helpful. @gray-kilobyte-89541 @nutritious-restaurant-91514
  • p
    Your link helped me a lot, but now I have problem with using this assertion
  • p
    I want to click this button only when aria-check=false, but Cypress fails every time aria-checked is true instead of just skipping this step
  • p
    any ideas?
  • g
    are you on Windows? Then you have to set that process environment variable how Windows expects it, you are setting it Linux-style
  • g
    you are doing conditional testing (incorrectly), see https://glebbahmutov.com/cypress-examples/recipes/conditional-testing.html
  • p
    Wow, thanks @gray-kilobyte-89541, your knowledge is crazy!!!
  • p
    works like a charm
  • e
    Thanks a lot for getting back to me @gray-kilobyte-89541 Yes I'm on Windows, i tried setting it up in process.env (node), but doesn't seem to work ☹️ I also tried setting it up in Windows env variables, no luck either
  • n
    Hey there
  • g
  • n
    I am trying to run a spec file with 15 tests in it form Test runner, And always around 7 mins 15 secs the test runner goes to a white blank screen, will all tests gone!!!!
  • n
    Is it a system limitation ?/ like by design it doesn't support test execution more than x minis ?
  • g
    probably runs out of memory and crashes. Split the spec into shorter specs
1...424344...192Latest