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'm seeing a lot of unhelpful behavior with the screenshot feature of Cypress. For a site that makes a lot of background API requests, by the time the test fails, the failure has scrolled off-screen in CI. This means we literally can't debug the failure, since the error message is cryptic ("Timed out retrying after 10000ms: Expected to find element: >li:eq(2), but never found it."). We are displaying an assertion fail with a custom error message, but it isn't visible and doesn't show up in the junit xml.
This is with Cypress 10.8.0, but I have noticed this suboptimal behavior with all versions of Cypress 10.
Is this a bug to report, or are there workarounds?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm seeing a lot of unhelpful behavior with the screenshot feature of Cypress. For a site that makes a lot of background API requests, by the time the test fails, the failure has scrolled off-screen in CI. This means we literally can't debug the failure, since the error message is cryptic ("Timed out retrying after 10000ms: Expected to find element: >li:eq(2), but never found it."). We are displaying an assertion fail with a custom error message, but it isn't visible and doesn't show up in the junit xml.
This is with Cypress 10.8.0, but I have noticed this suboptimal behavior with all versions of Cypress 10.
Is this a bug to report, or are there workarounds?
Beta Was this translation helpful? Give feedback.
All reactions