You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like that Cypress outputs a retry-agnostic error message when retries are disabled by setting defaultCommandTimeout to 0 — or any other scoped timeout-related setting to disable retries.
Having a conditional error message to display the "Timed out retrying after ***ms" prefix only when retries are in place:
If retries are in place: Timed out retrying after ***ms: expected [...]
Otherwise: expected [...]
Why is this needed?
Considering we use Cypress to implement end-to-end tests of our REST API, it's confusing for stakeholders to read timeout-related messages.
API responses are not expected to change, thus the defaultCommandTimeout: 0 setting.
Other
No response
The text was updated successfully, but these errors were encountered:
As you mentioned, the change is quite easy, but I struggle to find the existing test suite covering the driver's retries.ts code. Could you point me in the right direction, please?
What would you like?
I'd like that Cypress outputs a retry-agnostic error message when retries are disabled by setting
defaultCommandTimeout
to0
— or any other scoped timeout-related setting to disable retries.Having a conditional error message to display the "Timed out retrying after ***ms" prefix only when retries are in place:
Timed out retrying after ***ms: expected [...]
expected [...]
Why is this needed?
Considering we use Cypress to implement end-to-end tests of our REST API, it's confusing for stakeholders to read timeout-related messages.
API responses are not expected to change, thus the
defaultCommandTimeout: 0
setting.Other
No response
The text was updated successfully, but these errors were encountered: