requestTimeout and responseTimeout should apply individually to each request in cy.wait([]) with array of requests

[DamienCassou]

Current behavior:

cy.wait() can be passed an array of aliases. This is good. However, it is not clear what the impact on the timeout is. cy.wait() has 2 timeouts, requestTimeout and responseTimeout.

I guess that if before requestTimeout all aliases have matched, then cy.wait() will be happy. But what if only a few of the aliases have matched while others have not matched yet?

From my experiment, passing several aliases to cy.wait() means:

"I want all requests to be sent before requestTimeout"

Desired behavior:

The current behavior makes sense but I was expecting a completely different semantics:

"I don't want to wait more than requestTimeout between a response is received and the next request is sent".

I think the documentation should be improved about that so I opened an issue on the cypress-documentation project.

Still, @jennifer-shehane believes that the semantics of cy.wait() could benefit from being changed to match what we both expect.

More information about my context: #6563.

Versions

• Cypress: 4.1.0
• OS: Fedora 31
• Browser: Chromium

[jennifer-shehane]

When using cy.wait(['@alias1', '@alias2']) Cypress will wait for all requests to complete within the given requestTimeout and responseTimeout, but I think they should individually wait for requestTimeout and responseTimeout for each initiated request.

I think the implementation is a bit trickier than what I've plainly written it as though. Also...probably a breaking change?