https://cypress.io logo
Join Discord
Powered by
Hi all, how do you handle multiple waits? Though i...
# general-chat
e
Hi all, how do you handle multiple waits? Though in my testRunner its passing but in CI its failing
a
Do you have a screenshot of the failure in CI? Normally they show up red, I think.
Ah nvm, think your screenshot shows everything
e
Hi @alert-motorcycle-49357 these his the CI
@alert-motorcycle-49357 and this is the Sorry Cypress dashboard
cause im comparing the knowgood vs the generated one.. knowngood are saved in my file..
it should pass if the gaCollection are complete
@alert-motorcycle-49357 i found a solution ,, i created a loop ,
looking good in CI and Sorry cypress
@alert-motorcycle-49357 i still see failures 😭
a
I'm not sure how much help I will be as the context seems quite complicated, and also I'm still learning Cypress. But some thoughts / questions: - What are some of the failures like on this most recent run? Still a difference in a GA path like for 
/confimation
as you had before? - I can't see the part where Cypress interacts with the app in your spec - it seems to intercept some requests, and then wait. I would normally expect something like a call to 
cy.visit
- can you tell me anything about that? Does it take place somewhere like in a before each?
I'm guessing a bit, but it kind of feels like we want to tell Cypress a list of all specific requests to intercept, and then wait for all of them. That's different from my understanding of what's currently happening, where all requests under the GA URL are collected and then examined afterwards.. I have a feeling that the dependency on timing is causing the CI build failures here. But if we could tell Cypress in advance what requests to intercept I think that could help
3 Views
PreviousNext
Powered by