https://cypress.io logo
Join Discord
Powered by
# help
  • c
    That will allow for the built in retry logic in cypress to not just retry the assertions in the .then but the entire chain.
  • a
    yeah, exactly that
  • a
    than you both, @abundant-apple-80156 I'll try adding viewPort height & width in cypress.json and see what happens. I'll also take a look at the 
    cy.wrap
    @colossal-car-14055 suggested thank you both
  • s
    Hi
  • s
    Can anyone help me ?
  • b
    yes
  • b
    if you ask a question
  • a
    @sticky-energy-17458 shoot
  • s
    I have multiple cards over website and I need to verify that certain text is existing on each card or not , so first I verify the number of cards appearing and then I need to verify that text is appearing on each of the card. I tried loop but it's not working
  • b
    I need to get an id value out my url or one of the requests but I'm not sure how I can do that. Does anyone happen to know?
  • a
    I enabled debug mode since cypress gets stuck in CI at a random test without displaying any error. I see this message 
    cypress:launcher chrome stderr: [0607/201915.992016:FATAL:memory.cc(38)] Out of memory. size=524288 +178ms
    after that aborts some requests and 
    cypress:server:util:process_profiler
    loops printing memory stats until CI pipeline time outs
  • a
    so, if im reading the logs well chrome gets out of memory
  • a
    do you know how can I solve this? I already set 
    --disable-dev-shm-usage
    if browser is chromium
  • a
    I noticed pipeline completes successfully if test are ran with electron instead of chrome but I get this in logs: 
    Failed to adjust OOM score of renderer with pid 995: Permission denied (13)
    and other errors logged that dont break the pipeline
  • a
    Possibly you need to have a bigger container running your tests
  • a
    Can you just regex it?
  • c
    👋 I've been evaluating Cypress for the company I work at and it really looks awesome. Say we have our dev envs in a remote Linux machine and we use VSCode in Windows to ssh into that to work on the app we are building. Any pointers as to how to get the Cypress UI working in this scenario during development? I hope I make sense.
  • a
    Sort of depends if you are looking to run Cypress against dev environments as a TDD practice, or against built-and-hosted environments as e2e QA process.
  • c
    thanks! the latter would be more like it
  • c
    well, I guess that would not be entirely true, because at this point I would like to add the tests to the existing codebase and it would be important to "see" what we are doing with the test itself? I understand that we could integrate Cypress into the CI pipeline (headless mode?), but that is not the goal right now if that is where you were going
  • a
    If you want to run your tests against 
    test.domain.com
    then you can just write and run them on your local machine and ignore your dev environment. If you want to run your tests against 
    localhost
    then you'll need Cypress running on your dev VMs.
  • a
    We run our tests against hosted environments, so in a QA context, not a TDD context for devs.
  • a
    but both approaches have value.
  • c
    ahh, gotcha
  • c
    yes, that makes sense
  • a
    we write them and run them locally to make sure the tests are valid, then we run them in CI as a cron job.
  • a
    in every case we are targeting a hosted env though, not 
    localhost
  • c
    right, I think if we can reach the hosted env from the "locally installed Cypress" we should be good to go, at least as a start 🤔
  • a
    or that.
  • a
    if you do choose to ever implement Cypress in CI, I really recommend the Cypress Dashboard for playback and debugging.
1...787980...252Latest