Anything you could share about how cypress is organised when dealing with several applications? E.g. application A interacts with B and C. Putting a new version of A on staging. Is there a single cypress test suite covering all applications? Or does each application have it's own cypress test suite?
For Coolblue's webshop we've chosen to mock most of our dependencies between applications, not making it a fuuuully E2E test, but it's a choice to be made.
Cypress' documentation has a really nice article explaining the benefits and downsides of choosing different strategies to handle dependencies, I hope this helps :)
Interesting, thx for the blogpost!
Anything you could share about how cypress is organised when dealing with several applications? E.g. application A interacts with B and C. Putting a new version of A on staging. Is there a single cypress test suite covering all applications? Or does each application have it's own cypress test suite?
Hi Tibo, great question!
For Coolblue's webshop we've chosen to mock most of our dependencies between applications, not making it a fuuuully E2E test, but it's a choice to be made.
Cypress' documentation has a really nice article explaining the benefits and downsides of choosing different strategies to handle dependencies, I hope this helps :)
docs.cypress.io/guides/guides/netw...